Device assisted services install

ABSTRACT

Device assisted services (DAS) install techniques are provided in accordance with some embodiments. In some embodiments, DAS install techniques for providing service processors for mobile devices are provided. In some embodiments, DAS install techniques for downloading/installing new and/or updated service processors for mobile devices are provided. In some embodiments, DAS install techniques for providing verified service processors for mobile devices are provided. In some embodiments, DAS install techniques for providing secured service processors for mobile devices are provided. In some embodiments, DAS install techniques include determining if a communications device in communication with a wireless network includes a service processor for assisting control of the communications device use of a service on the wireless network, in which the service processor includes a service profile that includes a plurality of service policy settings, and in which the service profile is associated with a service plan that provides for access to the service; and verifying the service processor. In some embodiments, DAS install techniques include providing a generic first version service processor for downloading and installing a second version service processor.

BACKGROUND OF THE INVENTION

With the advent of mass market digital communications, applications andcontent distribution, many access networks such as wireless networks,cable networks and DSL (Digital Subscriber Line) networks are pressedfor user capacity, with, for example, EVDO (Evolution-Data Optimized),HSPA (High Speed Packet Access), LTE (Long Term Evolution), WiMax(Worldwide Interoperability for Microwave Access), DOCSIS, DSL, andWi-Fi (Wireless Fidelity) becoming user capacity constrained. In thewireless case, although network capacity will increase with new highercapacity wireless radio access technologies, such as MIMO(Multiple-Input Multiple-Output), and with more frequency spectrum andcell splitting being deployed in the future, these capacity gains arelikely to be less than what is required to meet growing digitalnetworking demand.

Similarly, although wire line access networks, such as cable and DSL,can have higher average capacity per user compared to wireless, wireline user service consumption habits are trending toward very highbandwidth applications and content that can quickly consume theavailable capacity and degrade overall network service experience.Because some components of service provider costs go up with increasingbandwidth, this trend will also negatively impact service providerprofits.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the followingdetailed description and the accompanying drawings.

FIG. 1 illustrates a wireless network architecture for providing deviceassisted services (DAS) install techniques in accordance with someembodiments.

FIG. 2 illustrates another wireless network architecture for providingDAS install techniques in accordance with some embodiments.

FIG. 3 illustrates a flow diagram for DAS install techniques inaccordance with some embodiments.

FIG. 4 illustrates another flow diagram for DAS install techniques inaccordance with some embodiments.

FIG. 5 illustrates another flow diagram for DAS install techniques inaccordance with some embodiments.

FIG. 6 illustrates a network architecture including a Universal MobileTelecommunications System (UMTS) overlay configuration in accordancewith some embodiments.

FIG. 7 illustrates a network architecture for an open developer platformfor virtual service provider (VSP) partitioning in accordance with someembodiments.

FIG. 8 illustrates a hardware diagram of a device that includes aservice processor in accordance with some embodiments.

FIG. 9 is a functional diagram illustrating a device based serviceprocessor and a service controller in accordance with some embodiments.

FIG. 10 illustrates a network architecture including a system located inthe manufacturing or distribution chain for the device that provides thedevice provisioning or partial provisioning, and any pre-activationrequired for the device to later activate on the network in accordancewith some embodiments.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as aprocess; an apparatus; a system; a composition of matter; a computerprogram product embodied on a computer readable storage medium; and/or aprocessor, such as a processor configured to execute instructions storedon and/or provided by a memory coupled to the processor. In thisspecification, these implementations, or any other form that theinvention may take, may be referred to as techniques. In general, theorder of the steps of disclosed processes may be altered within thescope of the invention. Unless stated otherwise, a component such as aprocessor or a memory described as being configured to perform a taskmay be implemented as a general component that is temporarily configuredto perform the task at a given time or a specific component that ismanufactured to perform the task. As used herein, the term ‘processor’refers to one or more devices, circuits, and/or processing coresconfigured to process data, such as computer program instructions.

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of the invention. The invention is described in connectionwith such embodiments, but the invention is not limited to anyembodiment. The scope of the invention is limited only by the claims andthe invention encompasses numerous alternatives, modifications andequivalents. Numerous specific details are set forth in the followingdescription in order to provide a thorough understanding of theinvention. These details are provided for the purpose of example and theinvention may be practiced according to the claims without some or allof these specific details. For the purpose of clarity, technicalmaterial that is known in the technical fields related to the inventionhas not been described in detail so that the invention is notunnecessarily obscured.

Device assisted services (DAS) install techniques are provided inaccordance with some embodiments. In some embodiments, DAS installtechniques for providing service processors for mobile devices areprovided. In some embodiments, DAS install techniques fordownloading/installing new and/or updated service processors for mobiledevices are provided. In some embodiments, DAS install techniques forproviding verified service processors for mobile devices are provided.In some embodiments, DAS install techniques for providing securedservice processors for mobile devices are provided. In some embodiments,DAS install techniques include providing a generic first version serviceprocessor for downloading and installing a second version serviceprocessor. These and other DAS install techniques are described hereinwith respect to various embodiments.

In some embodiments, a virtual network overlay includes a device serviceprocessor, a network service controller and a control planecommunication link to manage various aspects of device based networkservice policy implementation. In some embodiments, the virtual networkoverlay networking solution is applied to an existing hierarchicalnetwork (e.g., for wireless services), and in some embodiments, isapplied to simplify or flatten the network architecture as will befurther described below. In some embodiments, the large majority of thecomplex data path network processing required to implement the richerservice management objectives of existing hierarchical networks (e.g.,for wireless services) are moved into the device, leaving less data pathprocessing required in the edge network and in some cases even less inthe core network. Because the control plane traffic between the servicecontrol servers and the device agents that implement service policiescan be several orders of magnitude slower than the data plane traffic,service control server network placement and back-haul infrastructure ismuch less performance sensitive than the data plane network. In someembodiments, as described further below, this architecture can beoverlaid onto all the important existing access network architecturesused today. In some embodiments, this architecture can be employed togreatly simplify core access network routing and data plane trafficforwarding and management. For example, in the case of wirelessnetworks, the incorporation of device assisted service policyimplementation architectures can result in base stations that directlyconnect to the Internet local loop and the data traffic does not need tobe concentrated into a dedicated core network. This results, forexample, in a large reduction in backhaul cost, core network cost andmaintenance cost. These cost savings can be re-deployed to purchase andinstall more base stations with smaller cells, which results in higherdata capacity for the access network leading to better user experience,more useful applications and lower service costs. This flattenednetworking architecture also results in latency reduction as fewerroutes are needed to move traffic through the Internet. In someembodiments, the present invention provides the necessary teaching toenable this powerful transformation of centralized network servicearchitectures to a more distributed device based service architectures.

FIG. 6 illustrates a network architecture including a Universal MobileTelecommunications System (UMTS) overlay configuration in accordancewith some embodiments. As shown, FIG. 6 includes a 4G/3G/2GHSPA/Transport access network operated by a central provider and twomobile virtual network operator (MVNO) networks 210 operated by two MVNOpartners. In some embodiments, the central provider can offer improvedservice capabilities using a conventional UMTS network. As shown, thebase stations 125 do not connect directly to the Internet 120, andinstead the base stations 125 connect to the conventional UMTS network.However, the service processor 115 still connects through the securecontrol plane link to service controller 122. In some embodiments, thedata plane traffic is backhauled across the various UMTS network routersand gateways as is the control plane traffic, and the Internet protocoldetail records (IPDRs) are obtained from the access network AAA server121. Referring now to the 4G/3G/2G HSPA/Transport access network asshown in FIG. 6, the LTE/HSPA and HSPA/GPRS base stations/nodes 125 arein communication with 4G/3G/2G Service/Serving GPRS Support Nodes(SGSNs) cluster 410 via a radio access network 405, which are incommunication with 4G/3G/2G Gateway GPRS Support Nodes (GGSNs) cluster420 via an access transport network 415 (e.g., a GPRS-IP network), whichare then in communication with central provider core network 110.

As shown in FIG. 6, service usage data store 118 is a functionaldescriptor for a network level service usage information collection andreporting function located in one or more of the networking equipmentboxes attached to one or more of the sub-networks in the figure (e.g.,RAN, transport and/or core networks). As shown in FIG. 6, service usage118 is an isolated function connected to the central provider corenetwork 110 and the intention of this depiction is to facilitate all thepossible embodiments for locating the service usage 118 function. Insome UMTS network embodiments, the service usage 118 function is locatedor partially located in the GGSN gateway (or gateway cluster) 420. Insome embodiments, service usage 118 functionality is located orpartially located in the SGSN gateway (or gateway cluster) 410. In someembodiments, service usage 118 functionality is located or partiallylocated in the equipment cluster that includes the AAA 121 and/or themobile wireless center 132. In some embodiments, service usage 118functionality is located or partially located in the base station, basestation controller and/or base station aggregator, collectively referredto as base station 125 in FIG. 6. In some embodiments, service usage 118functionality is located or partially located in a networking componentin the transport network 415, a networking component in the core network110, the billing system 123 and/or in another network component orfunction. This discussion on the possible locations for the networkbased service usage history logging and reporting function can be easilygeneralized by one of ordinary skill in the art (e.g., RAN Gateway 410and/or Transport Gateway 420), and this background will be assumed evenif not directly stated in all discussion above and below.

In some embodiments, a central provider provides open developmentservices to MVNO, Master Value Added Reseller (MVAR) and/or OriginalEquipment Manufacturer (OEM) partners. In some embodiments, all threeservice providers, central provider service provider, MVNO #1 serviceprovider and MVNO #2 service provider have service control and billingcontrol of their own respective devices 100 through the unique pairingof the service processors 115 and service controllers 122. For example,MVNO #1 and MVNO #2 can each have open development billing agreementswith the central provider and each can own their respective billingsystems 123. As shown in FIG. 6, MVNO #1 core network 210 is incommunication with the central provider core network 110 via theInternet 120, and MVNO #2 core network 210 is in communication with thecentral provider core network 110 via an alternate landline(LL)/VPNconnection 425. In some embodiments, the two MVNOs each offer completelydifferent devices and/or services, and the devices and/or services alsodiffer significantly from those offered by the central provider, and theservice profiles are adapted as required to service the differentdevices and respective service offerings. In addition, the centralbilling system 123 allows all three service provider user populations toaccess ecommerce experiences from transaction provider partnersoperating transaction servers 134, to choose central provider billingoptions that combine their third party transaction bills on theirservice provider bill, and each subscriber population can experience aservice provider specified look and feel that is unique to therespective service provider even though the different user populationsare interfacing to the same transaction servers and the transactionpartners do not need to require significant custom development toprovide the unique central billing and unique consistent user experiencelook and feel.

In some embodiments, a central provider offers open network device andservice developer services using one service controller server 122(e.g., a service controller server farm) and allows the open developmentpartners to lease server time and server tools to build their ownservice profiles. The central provider also provides service billing onbehalf of services to the open development partners. For example, thisreduces costs associated with setting up an MVNO network for the opendevelopment partners and does not require the partners to give upsignificant control or flexibility in device and/or service control.

In some embodiments, virtual service provider (VSP) capabilities includemaking available to a third party service partner one or more of thefollowing: (1) device group definition, control and security, (2)provisioning definition and execution, (3) ATS activation owner, (4)service profile definitions, (5) activation and ambient servicedefinition, (6) billing rules definition, (7) billing process andbranding controls, (8) bill by account settings, (9) service usageanalysis capabilities by device, sub-group or group, (10) beta testpublishing capabilities by device, sub-group or group, and (11)production publishing, fine tuning and re-publishing.

FIG. 7 illustrates a network architecture for an open developer platformfor virtual service provider (VSP) partitioning in accordance with someembodiments. As shown, the service controller design, policy analysis,definition, test, publishing system 4835 is configured so that multiple“service group owners” (e.g., the service provider for certain smartphones) or “device group owners” (e.g., eReader devices for the eReaderservice provider(s)) or “user group owners” (e.g., IT for Company X fortheir employees' corporate mobile devices), collectively referred to asthe “Virtual Service Provider” (VSP), are serviced with the same servicecontroller infrastructure and the same (or substantially similar)service processor design from virtual service provider workstationserver 4910 and/or virtual service provider remote workstation(s) 4920.As shown, the virtual service provider remote workstation(s) 4920communicates with the virtual service provider workstation server 4910via VPN, leased line or secure Internet connections. The dashed linesshown in FIG. 7 are depicted to represent that, in some embodiments, thevirtual service provider workstation server 4910 is networked with theservice controller device control system 4825 and/or, in someembodiments, the service controller design, policy analysis, definition,test, publishing system 4835. Based on the discussion herein, it will beapparent to one of ordinary skill in the art that the VSP workstationserver 4910 can also be networked in various embodiments with billingsystem 123, AAA server 121, gateways 410 or 420, or other networkcomponents to perform, for example, various network provisioning andactivation related functions discussed herein for the device groupassigned to one or more VSPs, or for other reasons as will be apparentto a given VSP embodiment.

In some embodiments, the service controller functionality is partitionedfor a VSP by setting up one or more secure workstations, secure portals,secure websites, secure remote software terminals and/or other similartechniques to allow the service managers who work for the VSP toanalyze, fine tune, control or define the services they decide topublish to one or more groups of devices or groups of users that the VSP“owns.” In some embodiments, the VSP “owns” such groups by virtue of arelationship with the central provider in which the VSP is responsiblefor the service design and profitability. In some embodiments, thecentral provider receives payment from the VSP for wholesale accessservices. In some embodiments, the VSP workstations 4910 and 4920 onlyhave access to the service analysis, design, beta testing and publishingfunctions for the devices or users “owned” by the VSP. In someembodiments, the user or device base serviced by the central providernetwork is securely partitioned into those owned by the centralprovider, those owned by the VSP, and those owned by any other VSPs.

In some embodiments, the VSP manages their devices from the VSPworkstations 4910 and 4920 using device based service control techniquesas described herein. In some embodiments, the VSP manages their devicesfrom the VSP workstations 4910 and 4920 using device assisted andnetwork based service control techniques as described herein. In someembodiments, the VSP manages their devices from the VSP workstations4910 and 4920 using network based service control techniques (e.g., DPItechniques) as described herein.

For example, this approach is particularly well suited for “opendeveloper programs” offered by the central providers in which thecentral provider brings in VSPs who offer special value in the devicesor service plans, and using this approach, neither the central providernor the VSP needs to do as much work as would be required to set up aconventional MVNO or MVNE system, which often requires some degree ofcustomization in the network solution, the billing solution or thedevice solution for each new device application and/or serviceapplication that is developed and deployed. In some embodiments, theservice customization is simplified by implementing custom policysettings on the service processor and service controller, and the customdevice is quickly brought onto the network using the SDK andtest/certification process. In some embodiments, the VSP functionalityis also offered by an entity other than the central provider. Forexample, an MVNE entity can develop a wholesale relationship with one ormore carriers, use the service controller to create the VSPcapabilities, and then offer VSP services for one network or for a groupof networks. In some embodiments, the service customization issimplified by implementing custom policy settings through the VSPembodiments on the network equipment, including, in some embodiments,service aware or DPI based network equipment that has a relatively deeplevel of service activity control capability. For example, using theembodiments described herein, and possibly also including some of theactivation and provisioning embodiments, it is possible to efficientlydesign and implement custom ambient service plans that are different fordifferent types of devices, different OEMs, different VSPs, differentdistributors, or different user groups all using the same generalinfrastructure, whether the service control policy implementation isaccomplished primarily (or exclusively) with networking equipment(network) based service control, primarily (or exclusively) with devicebased service control or with a combination of both (e.g., hybrid deviceand network based service control).

As discussed herein, various VSP embodiments for performing one or moreof analyzing traffic usage and defining, managing service profiles orplans, dry lab testing service profiles or plans, beta testing serviceprofiles or plans, fine tuning service profiles or plans, publishingservice profiles or plans, or other policy related settings can involveprogramming settings in the network equipment and/or programmingsettings or software on the device. For example, as discussed herein,the service processor settings are controlled by the service controller,which can be partitioned to allow groups of devices to be controlled. Asanother example, equipment in the network involved with network basedservice control, such as DPI based gateways, routers or switches, cansimilarly be programmed to utilize various VSP embodiments to implementthat portion of the service profile (or service activity usage control)that is controlled by network level functions, and it will beappreciated that substantially all or all of the service activitycontrol for certain embodiments can be accomplished with the networkfunctions instead of the device. Continuing this example, just as thedevice service processor settings control functions of the serviceprocessor can have a group of devices that are partitioned off andplaced under the control of a VSP, various VSP control embodiments canpartition off a group of devices that have service usage activitycontrolled by the networking equipment, including, in some embodiments,sophisticated service aware DPI based service control equipment, toachieve similar objectives. It will be appreciated that the discussionherein regarding service controller design, policy analysis, test,publishing 4835, and the discussion regarding device group, user groupand other VSP related embodiments, should be understood as applicable tovarious embodiments described in view of device based services control,control assistance and/or monitoring, or network based services control,control assistance and/or monitoring, or a combination of device basedservices control, control assistance and/or monitoring and network basedservices control, control assistance and/or monitoring. The variousembodiments described herein related to service activation andprovisioning also make apparent how the programming of network equipmentservice control, service control assistance and/or monitoring can beimplemented prior to and following activation of the device. It willalso be appreciated that the VSP capabilities described herein can alsobe applied to those devices that have services controlled by, providedby and/or billed by the central provider, so these techniques can beapplied to central provider service embodiments, MVNO embodiments andother embodiments.

In some embodiments, an SDK is provided that allows developers, such asdevice manufacturers, service providers, MVNO, MVNE and/or VSPs, todevelop various service processors (e.g., different versions of theservice processor 115) for various devices (e.g., various types ofdevices 100) and corresponding service controllers (e.g., differentversions of the service controller 122) for various types of servicesand network environments. For example, a device manufacturer can use theSDK to develop a new service processor for their new device (e.g.,mobile phone, PDA, eBook reader, portable music device, computer,laptop, netbook, or any other network accessible device). The devicemanufacturer can also preload/preinstall their new service processor ontheir new devices. In this example, users of the new device would thenbe able to utilize the new device to access network based services usingthe new service processor, which communicates with the deployed newservice controller, as similarly discussed herein in variousembodiments. For example, the device can be preinstalled with the newservice processor to provide ambient services, as similarly discussedherein in various embodiments. For example, the SDK can allow forsubstantially similar service processors to be installed on similarand/or different devices thereby minimizing any unnecessary differencesbetween service processor elements for device assisted services. In someembodiments, for ambient services for a group of devices, or devicesassociated with a certain service provider, a set of numbers (e.g.,dummy numbers) can be assigned for use for attempting access via theaccess network using a new device that is not yet otherwise subscribedfor service. In some embodiments, the set of (dummy) numbers used forambient access by the device can also be used for associating the devicewith a service provider or a type of device (e.g., eReader or some othertype of network accessible device), and upon activation, the serviceprovider assigns a real number for the activated device (e.g., which canbe provided at the time of manufacture of the device, point of sale ofthe device, or after the point of sale of the device, such as uponactivation of the device). For example, ambient access of the device canuse the device ID, SIM ID, assigned phone (real or dummy) number, and/orother information associated with the device for assigning appropriateservice control and service policy/profile for the device.

In some embodiments, the service processor 115 is distributed as an SDKto any device that the central provider or the VSP desires to offerservices with so that the service processor 115 can be efficientlydesigned or adapted by the device OEM, ODM or manufacturer for operationon the service network. In some embodiments, the SDK includes either acomplete set of service processor 115 agent software designed for and/ortested for the OS (Operating System) and processor set being used on thedevice, or a mature reference design for the OS and processor set beingused on the device, or a less mature reference design (potentially forthe same OS and/or processor set or a different OS and/or processor setbeing used on the device) that the OEM (Original Equipment Manufacturer)ports to the desired OS or processor set, or a basic set of examplesoftware programs that the OEM or ODM (Original Design Manufacturer) canuse to develop software compatible with the service, or a set ofspecifications and descriptions (possibly forming an interoperabilitystandard) of how to design the software to be compatible with theservice. In some embodiments, the SDK includes a set of OEM lab testprocedures and/or test criteria to ensure that the implementation of theservice SDK is compatible with the service and will operate properly. Insome embodiments, the SDK includes a set of network certification testprocedures and/or test criteria to ensure that the implementation of theservice SDK is compatible with the service and will operate properly. Insome embodiments, the certification procedures are approved for testingby the OEM, the central provider, the VSP and/or a trusted third party.For example, the central provider is typically in control of the SDK andthe test procedures, but others can be in control. In some embodiments,the test procedures are at least in part common across multiple centralprovider networks. In some embodiments, the SDK concept is extended toinclude one or more modem modules where one or more of the SDKembodiments described above is combined with a standard reference designor a standard hardware sales package for one or more modems so that theentire package forms a turn-key product that allows a devicemanufacturer, central provider, VSP or other entity bring new devices ordevice applications onto the central provider network possibly incombination with other networks in a manner that requires lessengineering time and resources and less network certification time andresources than would be required in some designs that do not use thisstandard SDK plus module approach. For example, the standard SDK plusmodule product embodiments can be pre-certified and tested with one ormore central providers to further reduce development time and expense.The standard SDK plus module embodiments can also use a multi-mode modem(e.g., modems based on a multimode CDMA, EVDO, UMTS, HSPA chipset as inthe Gobi global multimode chipset product or modems based on otherrecently announced LTE plus HSPA chipsets, WiMax plus Wi-Fi chipsets orLTE plus EVDO chipsets) and a multi-mode connection manager agent sothat the same SDK plus modem embodiment may satisfy a wide range ofapplications for many service providers around the world.

In some embodiments, at the time of manufacture, the device isassociated with an MVNO. For example, the MVNO can provide an ambientservice that provides a service provider clearing house, in which thedevice can access a network in ambient access mode (e.g., a wholesaleMVNO connection through the access network) for purposes of selecting aservice provider (e.g., a VSP, MVNO or carrier). Based on the serviceprovider selection, the device credentials and/or service processor arereprogrammed and/or new software is downloaded/installed to activate thedevice with the selected service provider, as described herein forprovisioning the device and the account on that service provider network(e.g., the activation tracking service (ATS) can track such activation,for example, for revenue sharing purposes, as an activation incentivefee).

In some embodiments ATS is implemented entirely in the network. At thetime of manufacture or at sometime during device distribution, thedevice master agent programs a unique credential in the device thatcannot be re-programmed or removed (or is difficult to re-program orremove) and that can be recognized and recorded by the network at thetime of activation or at some other time. In this manner, even if other,possibly primary, device credentials are reprogrammed or removed, therewill still be a credential that is associated with the device masteragent. The ATS process can then be implemented by using a databasesearch function to scan through the database of activated devices toform a list of devices that have been activated for the purpose ofmaster agent reconciliation. Example credentials that can suffice areMEID, hardware MAC address, and/or serial number, that are picked up andrecorded by the service provider or other service entity at time ofactivation or before or after activation.

In some embodiments, the service processor 115 includes variouscomponents, such as device agents, that perform service policyimplementation or management functions. In some embodiments, thesefunctions include service policy or implementation verification, servicepolicy implementation tamper prevention, service allowance or denial,application access control, traffic control, network access controlservices, various network authentication services, service control planecommunication, device heartbeat services, service billing, transactionbilling, simplified activation services and/or other serviceimplementations or service policy implementations. It will be apparentto those of ordinary skill in the art that the division in functionalitybetween one device agent and another is a design choice, that thefunctional lines can be re-drawn in any technically feasible way thatthe product designers see fit, and that the placing divisions on thenaming and functional breakouts for device agents aids in understanding,although in more complex embodiments, for example, it can make sense tothe product designer to break out device agent functionalityspecifications in some other manner in order to manage developmentspecification and testing complexity and workflow.

FIG. 8 illustrates a hardware diagram of a device 100 that includes aservice processor 115 in accordance with some embodiments. As shown inFIG. 8, the service processor 115 is stored in a non volatile memory 910and a memory 920 of the device 100. As will be appreciated by those ofordinary skill in the art, the present invention can operate withvirtually any device architecture, and the device architecturesdiscussed herein are examples of various implementations on certaindevices (e.g., of different representations of device 100).

As shown in FIG. 8, device 100 also includes a processor 930, sometimesreferred to as a CPU or central processor unit, an APU or applicationprocessor unit, a core processor, a computing device, or many other wellknown terms. In some embodiments, device 100 includes one or moreprocessors and/or a multicore processor. As shown, processor 930includes a sub-processor 935. In some embodiments, processor 930 and/orsub-processor 935 are based on an architecture sometimes referred to asa complex instruction set computer or CISC, a reduced instruction setcomputer or RISC, a parallel processor, a combination of two or morearchitectures or any other processor architecture. In some embodiments,processor 930 has a design that is based on logic and circuitry from oneor more standard design library or published architecture, or includesspecialized logic and circuitry designed for a given device 100 orcollection of such devices. In some embodiments, a device includes morethan one processor and/or sub-processor, and in such a device, oneprocessor and/or sub-processor can have one architecture while anothermay have a somewhat different or completely different architecture. Insome embodiments, one or more of the processors and/or sub-processorscan have a general purpose architecture or instruction set, can have anarchitecture or instruction set that is partially general or partiallyspecialized, or can have an instruction set or architecture that isentirely specialized. In some embodiments, a device includes more thanone processor and/or sub-processor, and in such a device, there can be adivision of the functionality for one or more processors and/orsub-processors. For example, one or more processors and/orsub-processors can perform general operating system or applicationprogram execution functions, while one or more others can performcommunication modem functions, input/output functions, user interfacefunctions, graphics or multimedia functions, communication stackfunctions, security functions, memory management or direct memory accessfunctions, computing functions, and/or can share in these or otherspecialized or partially specialized functions. In some embodiments, anyprocessor 930 and/or any sub-processor 935 can run a low level operatingsystem, a high level operating system, a combination of low level andhigh level operating systems, or can include logic implemented inhardware and/or software that does not depend on the divisions offunctionality or hierarchy of processing functionality common tooperating systems.

As shown in FIG. 8, device 100 also includes non-volatile memory 910,memory 920, graphics memory 950 and/or other memory used for generaland/or specialized purposes. As shown, device 100 also includes agraphics processor 938 (e.g., for graphics processing functions). Insome embodiments, graphics processing functions are performed byprocessor 930 and/or sub-processor 935, and a separate graphics process938 is not included in device 100. As shown in FIG. 8, device 100includes the following modems: wire line modem 940, WWAN modem 942, USBmodem 944, Wi-Fi modem 946, Bluetooth modem 948, and Ethernet modem 949.In some embodiments, device 100 includes one or more of these modemsand/or other modems (e.g., for other networking/access technologies). Insome embodiments, some or all of the functions performed by one or moreof these modems are performed by the processor 930 and/or sub processor935. For example, processor 930 can implement some or all of certainWWAN functional aspects, such as the modem management, modem physicallayer and/or MAC layer DSP, modem I/O, modem radio circuit interface, orother aspects of modem operation. In some embodiments, processor 930 asfunctionality discussed above is provided in a separate specializedprocessor as similarly shown with respect to the graphics and/ormultimedia processor 938.

As also shown in FIG. 8, device 100 includes an internal (or external)communication bus structure 960. The internal communication busstructure 960 generally connects the components in the device 100 to oneanother (e.g., allows for intercommunication). In some embodiments, theinternal communication bus structure 960 is based on one or more generalpurpose buses, such as AMBA, AHP, USB, PCIe, GPIO, UART, SPI, I2C, Firewire, DisplayPort, Ethernet, Wi-Fi, Bluetooth, Zigbee, IRDA, and/or anyother bus and/or I/O standards (open or proprietary). In someembodiments, the bus structure is constructed with one or more customserial or parallel interconnect logic or protocol schemes. As will beapparent to one of ordinary skill in the art, any of these or other busschemes can be used in isolation and/or in combination for variousinterconnections between device 100 components.

In some embodiments, all or a portion of the service processor 115functions disclosed herein are implemented in software. In someembodiments, all or a portion of the service processor 115 functions areimplemented in hardware. In some embodiments, all or substantially allof the service processor 115 functionality (as discussed herein) isimplemented and stored in software that can be performed on (e.g.,executed by) various components in device 100. FIG. 8 illustrates anembodiment in which service processor 115 is stored in device memory, asshown, in memory 920 and/or non-volatile memory 910, or a combination ofboth. In some embodiments, it is advantageous to store or implementcertain portions or all of service processor 115 in protected or securememory so that other undesired programs (and/or unauthorized users) havedifficulty accessing the functions or software in service processor 115.In some embodiments, service processor 115, at least in part, isimplemented in and/or stored on secure non-volatile memory (e.g., nonvolatile memory 930 can be secure non-volatile memory) that is notaccessible without pass keys and/or other security mechanisms. In someembodiments, the ability to load at least a portion of service processor115 software into protected non-volatile memory also requires a securekey and/or signature and/or requires that the service processor 115software components being loaded into non-volatile memory are alsosecurely encrypted and appropriately signed by an authority that istrusted by a secure software downloader function, such as servicedownloader 1663 as discussed below (and as shown in FIG. 9). In someembodiments, a secure software download embodiment also uses a securenon-volatile memory. Those of ordinary skill in the art will alsoappreciate that all memory can be on-chip, off-chip, on-board and/oroff-board. In some embodiments, the service processor 115 which as shownin FIG. 8 is stored or implemented in non volatile memory 910 and memory920, can be implemented in part on other components in device 100.

FIG. 9 is a functional diagram illustrating a device based serviceprocessor 115 and a service controller 122 in accordance with someembodiments. For example, this provides relatively full featured devicebased service processor implementation and service controllerimplementation. As shown, this corresponds to a networking configurationin which the service controller 122 is connected to the Internet 120 andnot directly to the access network 1610. As shown, a data plane (e.g.,service traffic plane) communication path is shown in solid lineconnections and control plane (e.g., service control plane)communication path is shown in dashed line connections. As previouslydiscussed, it is understood that the division in functionality betweenone device agent and another is based on, for example, design choices,networking environments, devices and/or services/applications, andvarious different combinations can be used in various differentimplementations. For example, the functional lines can be re-drawn inany way that the product designers see fit. As shown, this includescertain divisions and functional breakouts for device agents as anillustrative implementation, although other, potentially more complex,embodiments can include different divisions and functional breakouts fordevice agent functionality specifications, for example, in order tomanage development specification and testing complexity and workflow. Inaddition, the placement of the agents that operate, interact with ormonitor the data path can be moved or re-ordered in various embodiments.For example, as discussed below in some embodiments, one or more of thepolicy implementation or service monitoring functions can be placed onone of the access modems located below the modem driver and modem bus inthe communication stack as illustrated in certain figures and describedherein. As discussed below, some simplified embodiment figuresillustrate that not all the functions illustrated in all the figures arenecessary for many designs, so a product/service designer can choose toimplement those functions believed to be most advantageous or sufficientfor the desired purposes and/or environment. The functional elementsshown in FIG. 9 are described below.

In some embodiments, the service control device link 1691 facilitatesanother important function, which is the download of new serviceprocessor software elements, revisions of service processor softwareelements, and/or dynamic refreshes of service processor softwareelements. There are many embodiments for such operations. In someembodiments, the software is received as a single file over the servicecontrol device link 1691. For example, the file can have encryption orsigned encryption beyond any provided by the communication link protocolitself. In some embodiments, the software files are segmented intosmaller packets that are communicated in multiple messages sent over theservice control device link 1691. In some embodiments, once the file(s)are received, or the segmented portions of the file(s) are received,they are communicated to a service downloader 1663 for file aggregationand installation, which, in some embodiments, is performed after furthermeasures to verify the service processor software are completed. In someembodiments, the files are sent using other delivery means, such adirect TCP socket connection to the service downloader 1663 or someother software installer, which can also involve secure transport andadditional levels of encryption.

In some embodiments, the policy control agent 1692 adapts low levelservice policy rules/settings to perform one or more of the followingobjectives: achieve higher level service usage or cost objectives,reduce network control channel capacity drain, reduce network controlplane server processing bandwidth, and/or provide a higher level of userprivacy or network neutrality while satisfying service usage or serviceactivity objectives. In some embodiments, the policy control agent 1692performs a policy control function to adapt instantaneous servicepolicies to achieve a service usage objective. In some embodiments, thepolicy control agent 1692 receives service usage information from theservice monitor agent 1696 to evaluate service usage history as comparedto service usage goals. In some embodiments, the policy control agent1692 uses service monitor 1696 service usage or service activity historyand various possible algorithm embodiments to create an estimate of thefuture projected service usage. In some embodiments, the policy controlagent 1692 uses a future projection of service usage to determine whatservice usage or service activity controls need to be changed tomaintain service usage goals. In some embodiments, the policy controlagent 1692 uses service usage history to perform a service usage orservice activity analysis to determine the distribution of service usageacross service usage elements within categories, such as usage byapplication, usage by URL, usage by address, usage by content type,usage by time of day, usage by access network, usage by location, and/orany other categories for classifying service usage. In some embodiments,the policy control agent 1692 uses the service usage distributionanalysis to determine which service usage elements or service activitiesare creating the largest service usage (e.g., if e-mail, socialnetworking, or multimedia/online video application categories arecreating the largest service usage).

In some embodiments, device based access control services are extendedand combined with other policy design techniques to create a simplifieddevice activation process and connected user experience referred toherein as ambient activation. In some embodiments, ambient accessgenerally refers to an initial service access in which such serviceaccess is in some manner limited, such as where service options aresignificantly limited (e.g., low bandwidth network browsing and/oraccess to a specific transactional service), limited bandwidth, limitedduration access before which a service plan must be purchased tomaintain service or have service suspended/disabled or throttled orotherwise limited/reduced/downgraded, and/or any other time based,quality based, scope of service limited initial access for the networkenabled device. In some embodiments, ambient activation is provided bysetting access control to a fixed destination (e.g., providing access toa portal, such as a web page (e.g., for a hotspot) or WAP (WirelessApplication Protocol) page, that provides the user with service planoptions for obtaining a service plan for the user desired access, suchas the service plan options for data usage, service types, time periodfor access (e.g., a day pass, a week pass or some other duration), andcosts of service plan(s)). In some embodiments, service data usage ofthe ambient activated device is verified using IPDRs (e.g., using thedevice ID/device number for the device 101 to determine if the devicehas been used in a manner that is out of plan for the service planassociated with the device 101, such as based on the amount of datausage exceeding the service plan's service data usage limits, out ofplan/unauthorized access to certain websites, and/or out ofplan/unauthorized transactions). In some embodiments, service data usageof the ambient activated device is verified by setting a maximum datarate in the policy control agent 1692 and if/when it is determined thatthe device is exceeding a specified data rate/data usage, then theservice data usage is throttled accordingly. In some embodiments,various other verification approaches are used for ambient activationpurposes.

In some embodiments, the billing agent 1695 detects and reports servicebilling events. In some embodiments, the billing agent 1695 plays a keyrole in transaction billing. In some embodiments, the billing agent 1695performs one or more of the following functions: provides the user withservice plan options, accepts service plan selections, provides optionson service usage notification policies, accepts user preferencespecifications on service usage notification policies, providesnotification on service usage levels, provides alerts when service usagethreatens to go over plan limits or to generate excess cost, providesoptions on service usage control policy, accepts choices on serviceusage control policy, informs policy control agent 1692 of userpreference on service usage control policy, provides billing transactionoptions and/or accepts billing transaction choices. In some embodiments,the billing agent 1695 interacts with transaction servers (e.g., opencontent transaction partner sites 134) to conduct ecommerce transactionswith central billing 1619.

In some embodiments, the service notification and billing interfacenotifies the user of expected network coverage (e.g., based on thedevice's current geography/location and the accessible networks for thedevice from that current geography/location) and displays options to theuser based on the expected network coverage information. In someembodiments, the service notification and billing interface notifies theuser of their current service usage at specified service usage pointsand displays various options to the user (e.g., service usage optionsand/or billing options). For example, the user's responses to thepresented options are recorded (e.g., stored locally on the device atleast temporarily for reporting purposes or permanently in a localconfiguration data store until such configuration settings are otherwisemodified or reset) and reported, such as to the billing server (e.g.,central billing 1619). For example, user input, such as selected optionsand/or corresponding policy settings, can be stored locally on thedevice via a cache system. As another example, the service notificationand billing interface displays options to the user for how the userwants to be notified and how the user wants to control service usagecosts, the user's input on such notification options is recorded, andthe cost control options (e.g., and the billing agent 1695 and policycontrol agent 1692) are configured accordingly. Similarly, the user'sinput on service plan options/changes can be recorded, and the serviceplan options/changes (e.g., and the billing agent 1695 and policycontrol agent 1692) are configured/updated accordingly. In anotherexample, the service notification and billing interface provides varioustraffic control profiles, such as for where the user requests assistancein controlling service usage costs (e.g., service data usage and/ortransactional usage related activities/costs). Similarly, the servicenotification and billing interface can provide various notificationoptions, such as for where the user wants advance warning on servicecoverage. In another example, the service notification and billinginterface provides options for automatic pre-buy at a set point inservice usage. In another example, the service notification and billinginterface provides the option to choose different notification and costcontrol options for alternative networks or roaming networks.

As shown in FIG. 9, the service processor 115 includes a serviceinterface or user interface 1697. In some embodiments, the userinterface 1697 provides the user with information and accepts userchoices or preferences on one or more of the following: user serviceinformation, user billing information, service activation, service planselection or change, service usage or service activity counters,remaining service status, service usage projections, service usageoverage possibility warnings, service cost status, service costprojections, service usage control policy options, privacy/CRM/GPSrelated options, and/or other service related information, settings,and/or options. For example, the user interface 1697 can collect serviceusage information from service monitor agent 1696 to update the localservice usage counter (and/or, alternatively, the service usageinformation is obtained from the service controller 122) to update userinterface service usage or service cost information for display to theuser. As another example, service billing records obtained from centralbilling system 1619 can be used to synchronize local service usagecounters and service monitor agent 1696 information to perform real-timeupdating of local service usage counters between billing system 1619synchronizations. As another example, the user interface 1697 candisplay options and accept user preference feedback, such as similarlydiscussed above with respect to user privacy/CRM/GPS filtering, trafficmonitoring and service controls. For example, the user interface 1697can allow the user of the device to modify their privacy settings,provide user feedback on service preferences and/or service experiences,modify their service profiles (e.g., preferences, settings,configurations, and/or network settings and options), to review serviceusage data (e.g., based on local service usage counters and/or otherdata monitored by the service processor 115), to receive various eventsor triggers (e.g., based on projected service usage/costs), and/or theuser interface 1697 can provide/support various other user input/outputfor service control and service usage.

In some embodiments, by providing the service policy implementation andthe control of service policy implementation to the preferences of theuser, and/or by providing the user with the option of specifying orinfluencing how the various service notification and control policies orcontrol algorithms are implemented, the user is provided with optionsfor how to control the service experience, the service cost, thecapabilities of the service, the manner in which the user is notifiedregarding service usage or service cost, the level of sensitive userinformation that is shared with the network or service provider entity,and the manner in which certain service usage activities may or may notbe throttled, accelerated, blocked, enabled and/or otherwise controlled.Accordingly, some embodiments provide the service control tobeneficially optimize user cost versus service capabilities orcapacities in a manner that facilitates an optimized user experience anddoes not violate network neutrality goals, regulations and/orrequirements. For example, by offering the user with a set of choices,ranging from simple choices between two or more pre-packaged servicecontrol settings options to advanced user screens where more detailedlevel of user specification and control is made available, someembodiments allow the service provider, device manufacturer, devicedistributor, MVNO, VSP, service provider partner, and/or other “entity”to implement valuable or necessary service controls while allowing theuser to decide or influence the decision on which service usageactivities are controlled, such as how they are controlled or throttledand which service usage activities may not be throttled or controlled insome manner. These various embodiments allow the service provider,device manufacturer, device distributor, MVNO, VSP, service providerpartner, or other “entity” to assist the user in managing services in amanner that is network neutral with respect to their implementation andservice control policies, because the user is making or influencing thedecisions, for example, on cost versus service capabilities or quality.By further providing user control or influence on the filtering settingsfor the service usage reporting or CRM reporting, various levels ofservice usage and other user information associated with device usagecan be transmitted to the network, service provider, devicemanufacturer, device distributor, MVNO, VSP, service provider partner,and/or other “entity” in a manner specified or influenced by the user tomaintain the user's desired level of information privacy.

As shown in FIG. 9, the service processor 115 includes the servicedownloader 1663. In some embodiments, the service downloader 1663provides a download function to install or update service softwareelements on the device. In some embodiments, the service downloader 1663requires a secure signed version of software before a download isaccepted. For example, the download can require a unique key for aparticular service downloader 1663. As another example, the servicedownloader 1663 can be stored or execute in secure memory or execute asecure memory partition in the CPU memory space. Those of ordinary skillin the art will appreciate that there are a variety of other securitytechniques that can be used to ensure the integrity of the servicedownloader 1663.

In some embodiments, improved and simplified processes for provisioninga device or user for service on a central provider network, an MVNOnetwork or a virtual service provider (VSP) on the central providernetwork are provided. In some embodiments, provisioning includes one ormore of the following: a process or result of assigning, programming,storing or embedding into the device and/or network a set ofcredentials, or otherwise providing the credentials to the user; thecredentials being at least in part carried on the device or with theuser; and/or at least a portion of or a counterpart to the credentialsbeing stored or recognized by the network so that the various networkelements responsible for admitting the device access to the appropriateservice activities do so once the device or user service is active.

As an example, as discussed herein, the credentials can include one ormore of the following: phone number, device identification number, MEIDor similar mobile device identifier, hardware security device ID,security signature or other security credentials, device serial number,device identification and/or credential information via securityhardware such as a SIM, one or more IP addresses, one or more MACaddresses, any other network address identifier, embedded devicedescriptive information block (static or programmable), security key,security signature algorithms, passwords or other secure authorizationinformation, service processor (or similar device client or agentsoftware) identifier or settings or version, device type identifier,browser (e.g., http, https, WAP, other browser client) headerinformation or similar identifier, browser token information or similaridentifier, browser cookie information or similar identifier, embeddedbrowser instructions, portal-client (e.g., interface or communicationagent that connects to a network portal used at least in part forprovisioning or activation for the device or by the user) headerinformation or similar identifier, portal-client token information orsimilar identifier, portal-client cookie information or similaridentifier, embedded portal-client instructions, service provider, OEM,master agent (service distributor), VSP, device service owneridentifier, distributor or master agent, and/or any information thenetwork can use to authorize network admission, provision the device,provision the network, activate service, authorize, associate or enablethe device with a provisioning sequence, associate or enable the devicewith one or more service profiles, associate or assist the device withan activation sequence, associate or enable the device with an ambientprofile or service experience, associate or enable the device with oneor more service plans or service capabilities, associate the device witha service provider or service owner, associate the device with an OEM ormaster agent, associate the device with a distributor or master agent,or associate the device with a device group, user group or user.

In some embodiments, provisioning includes assigning, programming orembedding into the device and/or network the information to define thelevel of service activity, referred to as a service profile, that thedevice is authorized to receive. In some embodiments, provisioning alsoincludes establishing the device settings and/or network settings todefine an ambient activation experience in which the device userreceives a set of services after (e.g., within a short period of timeafter) purchasing or otherwise obtaining or installing the devicewhether the device has or has not been registered and activated with thedevice user or device owner.

In some embodiments, the ambient experience is the user experience thatis available at the time the device is sold in the event the user hasnot yet signed up for a service plan. For example, the ambientexperience is defined by an ambient service profile, an ambient serviceplan and/or the other service usage activity control policies in effectin the network, on the device, or a combination of both. For example, ifthe device service processor is used in large part to define the ambientservice profile, then the initial provisioning and activation settingsin the service processor, and possibly the service controller, candefine the user service upgrade offering choices, network destinationaccess control possibilities, traffic control policies, mobile commercetransaction capabilities (e.g., which transaction websites, WAP sites orportals the user can access to purchase information, content, music,games and/or eBooks), possibly free news or weather or other modestbandwidth Internet services that are provided free of charge to enticethe user into using/upgrading the service or using the transactions orviewing advertisements, what advertisements are displayed to the user orwhat advertisement based websites the user is exposed to, certainapplications may have access while others are blocked (e.g., Internetbased text services have access but email downloads do not), or otherexample service capabilities. It will be apparent to one of ordinaryskill in the art that allowing all of these services, and blocking otherambient user service attempts (e.g., unpaid large file size Internetdownloads or uploads or movie viewing or other access that would consumebandwidth and cause the ambient service to be a potential source oflosses for the service provider) is made possible by the service profilecontrol capabilities of the service processor and/or the servicecontroller. The bill by account embodiments, as discussed herein, inwhich each service activity can, for example, be separately tracked withthe service monitor and other agents and server functions to produce abilling offset that allows categorization and mediation of differentbilling entities (accounts) provides the capability for the serviceprovider to individually account for the costs of each ambient serviceelement. This allows business models wherein the free access to the enduser is paid for or partially paid for by one or more service providerpartners who are billed for service access using the bill by accountcapabilities (e.g., the transaction partners pay for user access totheir transaction experience and perhaps pay a revenue share fortransaction billing, the advertising sponsored website partners pay fortheir access service share).

In some embodiments, automated provisioning and activation includesautomation of one or more of the following functions: (1) programmingdevice credentials or partial credentials and recording them in adatabase (or providing same when they are programmed into the device),(2) associating these credentials with the proper provisioning and/oractivation actions to be taken on the device and in the network, (3)directing the device to the proper activation function (e.g., activationserver) sequence when it attempts to connect to the network, (4)completing provisioning of the device, (5) programming the AAA, billingsystem, gateways, mobile wireless center and other network equipment tothe proper initial device service control settings, and (6) establishinga service account for the device.

In some embodiments, improved processes for activating service for adevice or user with a network service provided by a central providernetwork, an MVNO network or a VSP on the central provider network areprovided. In some embodiments, activation includes one or more of thefollowing: a process or result of associating a service account withdevice or user credentials; with the service account potentially furtherbeing associated with a service profile defining the service activitiesthat the device is authorized to access; creating or updating a serviceusage or billing record and associating it with the service account tocreate a service plan; and/or initiating service to the device or userin which the network equipment allows access to the appropriate level ofservice activities. In some embodiments, VSP embodiments include theprovisioning and activation apparatus embodiments of any or all forms.

In conventional mobile device provisioning systems, the provisioning andactivation process required to create a user service account and enablethe device to access the desired level of service activities can limitmass market, low cost or user friendly applications of the device orservice, because the process can often be cumbersome, time consumingand/or expensive for the service provider, service owner, master agent(service distributor), MVNO, VSP and/or user. Accordingly, the variousembodiments for provisioning and activation described herein simplifythe provisioning and activation process for mobile devices. In someembodiments, provisioning and activation for the device and/or thenetwork accommodates a wide variety of device types and service profiletypes, with the capability to perform the provisioning and activation ata number of points in the manufacturing, distribution, sales and usageprogression for the device, and the ability to either pre-activatebefore first device use or very quickly activate during first device use(or during some later use of the device).

In some embodiments, as described herein, the term provisioninggenerally refers to those actions/processes associated with programmingthe device with credentials or other device settings or softwareinstallations used to later activate the device, as well as, in someembodiments, creating database entries and other credential associationsin the network so that the network and/or device have the informationused to recognize the device or credentials and implement the servicepolicies in the service profile and/or service plan once the serviceprofile and/or service plan are activated. In some embodiments, asdescribed herein, the term activation generally refers to the process ofcreating or selecting the service plan and/or service profile,programming the settings that are used in each (e.g., required) networkfunction and/or each (e.g., required) device function so that the systemcan properly associate the device credentials with the appropriateservice activity policies, and then admitting the device onto thenetwork. The term activation can also refer in some embodiments to thecreation of a user or device service account, in some cases, with useror device owner information or billing information. In some embodiments,the process of provisioning amounts to assigning credentials to thedevice and programming a portion or all of the credentials on thedevice, entering a portion or all of the credentials in the variousnecessary network equipment databases so that the network components arecapable of identifying the device and associating it with the networkbased portion of the admission, traffic processing, service monitoring,billing, service limits and other policies that are eventually definedby the service profile and service plan.

Further examples of the network based service profile policies includenetwork access level, traffic routing, service monitoring, servicelimits and actions taken upon reaching service limits. Once the serviceprofile is created and activated during the activation process, thedevice credentials and the associated service profile are communicatedthroughout the necessary network elements so that each element canimplement its part of the network portion of the service profilepolicies. This process of propagating the service profile settings toall the required network equipment components is a portion of what isreferred to herein as activation in accordance with some embodiments. Insome embodiments, the activation process includes associating thecredentials with the proper service plan and/or service profile, andpossibly completing the process of programming the device functionsand/or network functions so that the device can be admitted to theappropriate level of network services. In some embodiments, activationalso includes the service processor software settings, configurations orinstalls for each function or agent in the service processor toimplement its part of the service profile, service plan, service billingor transaction billing policies. In some embodiments, activation alsoincludes the creation of entries in the various service accountdatabases and/or billing databases to create a user account or deviceowner account for the purpose of managing the user choices for serviceplan and other account information storage and management aspects, suchas maintaining status information, maintaining the central serviceprofile configuration, conducting reconciliation and billing exchanges,service usage history, and/or account history.

In some embodiments, the term credentials generally refers to the set ofinformation parameters that the network and/or device uses (e.g.,requires) to admit the device onto the network and associate it with theappropriate service profile and/or service plan. For example, thecredentials can include one or more of the following: phone number,device identification number, MEID or similar mobile device identifier,hardware security device ID, security signature or other securitycredentials, device serial number, device identification and/orcredential information via security hardware such as a SIM, one or moreIP addresses, one or more MAC addresses, any other network addressidentifier, embedded device descriptive information block (static orprogrammable), security key, security signature algorithms, passwords orother secure authorization information, service processor (or similardevice client or agent software) identifier or settings or version,device type identifier, browser (e.g., http, https, WAP, other browserclient) header information or similar identifier, browser tokeninformation or similar identifier, browser cookie information or similaridentifier, embedded browser instructions, portal-client (e.g.,interface or communication agent that connects to a network portal usedat least in part for provisioning or activation for the device or by theuser) header information or similar identifier, portal-client tokeninformation or similar identifier, portal-client cookie information orsimilar identifier, embedded portal-client instructions, serviceprovider, OEM, master agent (service distributor), VSP, device serviceowner identifier, distributor or master agent, and/or any informationthe network can use to authorize network admission, provision thedevice, provision the network, activate service, authorize, associate orenable the device with a provisioning sequence, associate or enable thedevice with one or more service profiles, associate or assist the devicewith an activation sequence, associate or enable the device with anambient profile or service experience, associate or enable the devicewith one or more service plans or service capabilities, associate thedevice with a service provider or service owner, associate the devicewith an OEM or master agent, associate the device with a distributor ormaster agent, or associate the device with a device group, user group oruser. In some embodiments, at least some of the credentials are uniqueto the device, and, in some embodiments, groups of devices share one ormore aspects of the credentials. In some embodiments, the term permanentcredentials generally refers to the set of credentials that include atleast a subset that are intended to be assigned to a device or user on apermanent basis. In some embodiments, the term temporary credentialsgenerally refers to the set of credentials that include at least asubset that are intended to be assigned to a device or user on atemporary basis. In some embodiments, temporary credentials areeventually replaced by permanent credentials. In some embodiments, atleast some elements in the temporary credentials (e.g., phone numberand/or access or authorization security credential) are used for morethan one device. In some embodiments, the temporary credentials arerecycled from one or more devices and used for one or more otherdevices, for example, when they remain unused for a period of time orwhen they are replaced with permanent credentials on one or moredevices. It should not be inferred from the term permanent credentialsthat permanent credentials are never recycled, for example, when theuser discontinues service or use of the credentials. Also, the termtemporary credentials does not imply that temporary credentials arealways temporary. In some embodiments, partial credentials orpre-activation credentials generally refer to a subset of credentialsthat are to gain access to limited network services for the purpose ofprovisioning of credentials and/or activation of a service plan orservice profile. For example, prior to a phone number being assigned, adevice can gain access to a limited set of network server destinationsin which embedded information contained in the device (e.g., the partialcredentials) is provided to the server, the server associates thatinformation with the proper additional credentials (including the phonenumber) to assign to the device and/or associates the information withthe proper service profile to activate service. In this example, partialcredentials can include device type, OEM, service provider, VSP, deviceidentification number, SIM, service processor configuration or someother information used by the server to determine what the credentialsshould be and the proper service profile.

In some embodiments, a permanent service account generally refers to theservice account that is permanently associated with the user and/ordevice. For example, this account includes an association with thedevice or user credentials, user information or billing information,service profile, billing profile, network authorization status and otheraspects that define the device or user service policies and billingpolicies. In some embodiments, the term temporary service accountgenerally refers to a service account that is temporarily set up andassociated with the device before some or all of the required permanentaccount information is available or entered for a device or user. Forexample, this account can be set up with an association with an actualuser, or can be set up with a mock user or unassigned user associationso that the network and billing system can recognize the credentials,authenticate the device, admit the device, provide the proper level ofservice activity control according to the service profile associatedwith the temporary service account, or collect the service activityusage information for various network and billing system accountingneeds before actual user information or billing information has beenentered into the network systems. For example, a temporary serviceaccount can make it possible or easier to use existing billing systemsor other network systems to provide simplified provisioning, simplifiedactivation or ambient services. A temporary service account can alsobecome a permanent service account by replacing mock user or unassigneduser information with actual user information, or a temporary serviceaccount may need to be replaced by a permanent service account whenactual user information needs to be entered into the network systems,possibly including the billing or service profile databases.

In some embodiments, temporary or permanent device credentials and otherinformation used/required for provisioning the device are generated withapparatus located at the manufacturer or in the distribution channel asdiscussed below. In some embodiments, the apparatus includes a localonsite server that typically shares some aspects of the provisioninginformation (e.g., phone number, phone number range, MEID or MEID range,SIM number or SIM number range, IP address or IP address range, MACaddress or MAC address range, other secure device credential elements)with a network provisioning database. In some embodiments, the apparatusincludes a server terminal, and the aforementioned portion of thecredentials is generated by the network and shared with the localprovisioning apparatus. In some embodiments, as will be discussed below,the provisioning credentials are in part generated in the network andshared with the device while it is connected online to an activationserver (e.g., activation server 160) that is connected to the accessnetwork. Similarly, there can be activation servers connected toapparatus in the manufacturing or distribution channel that servicedevice activation, or over the air or over the network apparatusconnected to an activation server, which in turn connects to the device,can be used to accomplish activation programming of the network anddevice as further discussed below.

In some embodiments, when a device is provisioned and entered into thenetwork provisioning database, it is associated with the automaticprovisioning and/or activation sequence the device is intended to gothrough once it connects to the network or to the apparatus that willcomplete the process. In some embodiments, one or more device parameters(e.g., service owner, device type, OEM, plan type, IP address, securitycredential and/or software version) are used to determine what theappropriate network provisioning steps and/or settings are forcompleting the provisioning and/or activation process, and thisassociation information is stored in the network provisioning databasefor propagation of the provisioning profiles or activation profiles tothe various network equipment elements. In some embodiments, the networkprovisioning database is provided (e.g., in the network) that associatesthe pre-activation provisioning information (e.g., generated, asdescribed herein, at time of manufacture, sometime during distribution,by the user on a website by a sales associate or other activationassistant, or by the network when a new device enters the automaticactivation process). For example, the pre-activation provisioninginformation informs the network whether or not to let the device onto anactivation sequence when the device attempts access, and in some cases,also instructs the network to direct the device to a specific activationsequence including, for example, an activation server (or otheractivation sequencing apparatus) sequence as described herein. In someembodiments, a central database is queried by other network equipment orthe central database is included in one or more of the network elements(e.g., the AAA server and/or billing system, mobile wireless center132), or the database is copied in part or in whole in various networkelements (e.g., the central database, AAA server, mobile wirelesscenter, billing system and/or gateways).

In some embodiments, propagating the network equipment provisioninginformation for a given device or group of devices is accomplished witha network provisioning system that has access to the networkprovisioning database and is capable of programming the appropriatenetwork equipment. In some embodiments, this network equipment isreferred to as “network management” equipment or “network provisioning”equipment. In some embodiments, there are several functions that takepart individually or in concert, including, for example, the AAA server121, service controller 122 (either with device based/assisted servicesthrough the service processor related embodiments or with network onlyembodiments as described herein), the mobile wireless center 132 (e.g.,including the home location register (HLR) or other similar functionreferred to by other industry terms), the activation server(s) 160,other network provisioning or management equipment attached to orassociated with the billing database system, and/or some other equipmentapparatus. In some embodiments, the local database on the device,database in the AAA server and/or database elsewhere in network isprovisioned to inform the gateway of the process for handling thepre-provisioned device according to, for example, the credentials. Forexample, if the device is not recognized or not authenticated onto theaccess network as an activated device with associated active serviceprofile and/or service plan, the device connection or communication canbe directed (or routed) to a generic activation server that provides anactivation sequence that is not necessarily determined by one or more ofthe specific device credential elements, partial credential elements,device profile or partial device profile that define something specificabout the activation sequence for the device. In another example, inwhich the device is not recognized or authenticated as an activateddevice with associated service profile and/or service plan, the devicecan be directed (or routed) to an activation service (or otheractivation sequencing apparatus) that uses some part of the credentialsor range of partial credentials or a portion of a partial or completedevice profile to determine a desired pre-determined device specific ordevice group specific activation sequence that is implemented by aspecific activation service sequence or other activation sequenceapparatus. In another example, in which the device is not recognized orauthenticated as an activated device with associated active serviceprofile and/or service plan, a portion of the device credentials orpartial credentials can be used as a look-up index into a database thatdetermines what the specific device activation sequence should be, andthe device can be directed (or routed) to a specific activation serversequence or other activation sequencing apparatus.

In some embodiments, a database in the AAA server or database elsewherein network is provisioned to inform the gateway what to do with apre-provisioned device according to the credentials. For example,devices can be authenticated (for activated devices), routed toactivation servers (or other activation sequencing apparatus) or deniedaccess. In some embodiments, the AAA server (and/or other networkelements) provide the above discussed look-up function for the abovegateway description in which a lookup database, locally stored or storedin a central database, is queried to provide secondary routinginformation to the specific or generic activation servers.

In some embodiments, the pre-provisioned database is located in thebilling system. In some embodiments, the billing system accesses thepre-provisioned database (e.g., stored on the billing system or anothernetwork element) for the purpose of setting up temporary accounts orpermanent accounts and associating those accounts with pre-activationstatus, activated free ambient or activated paying customer.

-   -   In some embodiments, for zero activation, all the required        pre-provisioning or programming of the above network elements,        or others, is coordinated by the network provisioning system at        some point after the partial or full device credentials have        been associated with the device or reserved for a particular        device type or service type. In some embodiments, the network        provisioning system also coordinates the information to or from        the device provisioning apparatus that is described elsewhere.

In view of the various embodiments described herein, it will beappreciated that many of the automated or background provisioning,activation and ambient embodiments described herein can be accomplishedwith network based approaches, device based approaches, ornetwork/device combination/hybrid based approaches. For example, whenthe access control for the provisioning process is accomplished in thedevice (e.g., a device based approach), the activation server can belocated anywhere on the Internet, and the device will ensure that theactivation process is conducted with the activation server whileblocking other traffic from occurring. As another example, some or allof the ambient provisioning programming steps become steps to programthe access control, traffic control, application control, bill byaccount rules, and/or other aspects in the service processor or servicecontroller as described herein.

In some embodiments, the provisioning apparatus described herein can bea computer located in the user's home or business, and the user or an ITmanager has access to a website that provides the provisioninginformation, in which the computer serves as the provisioning orsoftware programming apparatus. In some embodiments, the network itself,possibly through an activation server 160, website or other interface tothe device, becomes the provisioning apparatus, in some cases, with theassistance of software on the device to affect the programming ofprovisioning information from the network or the communication of devicecredentials or other information to the network. For example, thissoftware can be a background process that runs without user interaction,a portal/widget program, a web browser based program, a WAP browserbased program, and/or any other program that provides a counterpartfunction to the network functions effecting the provisioning (e.g.,activation server). In some embodiments, the activation server eitherinitiates a specific provisioning sequence if device software is presentto assist or routes to a website for manual entry if there is nosoftware present.

FIG. 10 illustrates another network architecture including a systemlocated in the manufacturing or distribution chain for the device thatprovides the device provisioning or partial provisioning, and anypre-activation required for the device to later activate on the networkin accordance with some embodiments. Device credential, software andsettings server 6420 provides a link to the network functions thatgenerate or provide device credentials, and/or associate devicecredentials with activation profiles or pre-activation profiles in thenetwork equipment (e.g., the billing system 123, service controllerdevice control system 6225, gateways 410, 420, base station 125,credential generation and association server 6410, activation server160, service download control server 1660 and/or other networkapparatus). For example, the link between the device credential,software and settings server 6420 to the central provider core networkequipment can be over the Internet 120 (e.g., a secure link over theInternet) as shown or over another connection such as a leased line. Thedevice credential, software and settings server 6420 obtains credentialsor partial credentials from the network apparatus that generates them,illustrated by the credential generation & association server 6410.Credential generation & association server 6410 need not be directlyconnected to the central provider core network 110 as shown, but can belocated elsewhere (e.g., in another location connected by a secureInternet link). Credential generation & association server 6410 assignscredentials, or partial credentials, for use by device credential,software and settings server 6420. When these credentials are assignedto a device, they are programmed, loaded or otherwise associated withthe device by device credential provisioning apparatus 6430, which isconnected to the device wirelessly or via a wire line connection.

In some embodiments, a device software loading and programming apparatus6440 provides software loading or device settings functions that form aportion or all of the provisioning or pre-provisioning deviceconfiguration, or form a portion or all of the device activation profileconfiguration, or form the device service owner, master agent or VSPdevice assignment or signature, and in some embodiments, using anactivation tracking service (ATS) system. As discussed herein, the ATSmonitors network connections and aspects of traffic that provide insightinto which networks the device 100 is gaining access to, in someembodiments, for the purpose of ensuring that an OEM, master agent,device service owner or VSP is being compensated for devices thatactivate on a service provider network. In some embodiments, the ATSagent connects to a server counterpart that records and, in someembodiments, also analyzes the service or network connection informationto make a determination of the type of access service the device isreceiving and, in some cases, determine which networks the device isactivated on. In some embodiments, the ATS is installed on the device ina manner that makes it difficult to tamper with or remove so that theentity that is intended to get credit for device service activation doesget credit (e.g., the ATS agent can be loaded into secure memory, it canbe installed with software that makes it difficult to de-install, it canbe installed on the modem possibly in secure memory, it can be installedin the BIOS, it can be installed deep in the OS kernel, it can beinstalled with one or more additional device agents that monitor the ATSagent and alert a network function or re-install it if tampered with).The SIM inventory 6450 is provided to illustrate that, in someembodiments, hardware elements (e.g., a SIM security module as shown) orhardware configurations are also installed or manipulated in device 100and these operations and the recording of the resulting associationsform a portion of the provisioning or pre-provisioning process.

In some embodiments, at the time the credentials or partial credentialsare loaded, programmed, set, installed, read from the device orotherwise recorded, they are, in some cases, all associated together ina database that allows for later identification of the device and itsappropriate provisioning and/or activation process through suchassociations. For example, this can involve reading device parameterssuch as MEID, MAC address, device type, or other information that isassociated with the information being loaded or configured on thedevice. As discussed herein, this credential configuration andassociation information is stored in the network equipment responsibleusing it to configure the network to activate the device in one of thevarious embodiments disclosed herein.

Some embodiments include tying some or all of the activationprovisioning steps and information settings together into a databasethat defines a higher level activation profile for a group ofusers(/devices), and a server is used to perform device and equipmentprogramming for the devices in the group, including, for example,associating the following device information into the group definition:credentials, service owner or master agent, provisioning informationand/or activation profile. Some embodiments further provide for thisdevice group information being distributed to the various networkequipment components required to activate the devices as discussedelsewhere. In some embodiments, this programming and device groupassociation is accomplished using the VSP workstation server 4910. Forexample, a device can be manufactured and distributed in a manner thatprovides flexible assignment of the device to a group that is assignedto an activation profile or a service owner.

In some embodiments, multiple activation servers 160 are provided (asshown), which illustrates that there can be multiple device activationservers 160 each with a different device activation experience andpotentially controlled by a different VSP, service owner, serviceprovider, OEM or master agent. As discussed herein, there are severalways that a device 100 can be routed to the proper activation server 160so that the device provisioning and activation process can be completed.In some embodiments, all devices that are not activated are re-directed(or routed) to an activation server that reads one or more parameters inthe device credentials. The device credential information can bedetermined either through the device identification informationassociated with the access network connection itself (e.g., MEID, IPaddress, phone number, security credentials, or other credentialsidentified for a device that gains access with the network), or with theaid of the device in a pre-arranged query-response sequence. The devicecan then be re-directed (or routed) to the appropriate activation serverfor that device, device group, device service owner or VSP. In someembodiments, the same process described above can be accomplished with asingle re-direction from a service gateway 420 or 410, or another routerenable network element. In some embodiments, the gateway or networkelement itself decodes the device credential information as describedherein and performs the correct re-direct (or route) to the appropriateactivation server 160 for that device. In some embodiments, theactivation server 160 can be incorporated directly into the gateway 420or 410, the base station 125 or other network component. In someembodiments, the activation server 160 can be incorporated into theservice controller 122 or the service controller device control system6225.

In some embodiments, apparatus other than the activation server are usedto facilitate provisioning of credentials or partial credentials, oractivation, during manufacturing or device distribution, and, forexample, these apparatus can augment, supplement, compliment or replacethe activation server function. Such apparatus include, for example,device programming equipment (e.g., device credential provisioningapparatus 6430, device software loading and programming apparatus 6440or SIM inventory 6450), equipment that is networked into a centralprovider, MVNO or VSP database (e.g., device credential, software andsettings server 6420) to gain access to provisioning information oractivation information that is programmed into a device or group ofdevices, or to place device credential or partial credential informationin a network database for later recognition, or to receive orcommunicate security information such as certificates for devices or SIMmodules that will later be used to complete provisioning or completeactivation or gain access to a network. For example, these apparatus, orany other apparatus including the activation server, can be networkedinto a service provider network or device database, an MVNO network ordevice database or a VSP network or device database. In someembodiments, programming of the device credentials or other informationassociated with the service processor or device is provided, so that,for example, the device can be recognized by an activation server orsimilar network function at a later point in time so that provisioningor activation can be completed in an automated manner, potentially withreduced or no user involvement, that provides a provisioning oractivation configuration that is in some way unique for the serviceprovider or service provider partner, device type, user group, VSP,MVNO, master agent or other entity. In some embodiments, thisprogramming is provided in a manner that is difficult to change withoutthe proper authorization so that the device is properly associated withthe proper “service owner” or master agent (e.g., for the purpose ofactivation incentive payments). For example, as discussed herein,various approaches can be applied to the device credential or othersettings or software provisioning so that the settings or software aresecure or protected, or so that if the software is removed, replaced ormodified it is reported or replace or restored. In some embodiments, VSPcontrol of the provisioning, partial provisioning or activation ofdevices is provided during manufacture or at different points in thedistribution channel. As discussed herein, some of these embodimentsallow the central provider to offer to service partners (e.g., VSPs,MVNOs, master agents, and/or OEMs) similar types of control for deviceactivation experience design or device service assignment control (e.g.,sometimes referred to as service provider device locking so that otherservice providers cannot provide primary access to the device) duringthe manufacturing or distribution process that are possible with devicesmanufactured and distributed for the central service provider.

In some embodiments, the device is provisioned before the user obtainsthe device with permanent credentials, temporary credentials or partialcredentials. In this case, the necessary credential programming of thedevice occurs during manufacture, at some point in the devicedistribution, such as at a distribution depot or in a store, or at thepoint of sale or point of shipment. In some embodiments, provisioning ofnetwork information as discussed above is used, and the networkinformation is provisioned at the same time, before or after the deviceinformation is provisioned. In some embodiments, the device provisioninginformation is programmed with dedicated apparatus that connects to thedevice either with wires or wirelessly. For example, the dedicatedapparatus can be local to the location where the device is beingprovisioned, or it can be partially or entirely networked into adatabase or provisioning solution located elsewhere and operated by thecentral provider, a VSP, OEM or other entity. For example, the apparatusto program the network portions of the provisioning information can alsobe networked and the operators who set up the required networkprogramming for a device or group of devices may be in the vicinity ofthe servers that host the provisioning and management tools or they maynetwork into the servers. In some embodiments, provisioning systemoperators have full or partial control of any device provisioningequipment associated with the entity they work for (e.g., OEM, VSP ormaster agent) but only have remote access via secure terminal, securewebsite or other techniques to network into a central provider or VSPserver farm in which they control or partially control the networkportion of provisioning capabilities for that subset of devices that areassigned to the entity they work for with (e.g. OEM, VSP or masteragent).

In some embodiments, provisioning is accomplished over the air on themobile access network for mobile devices, or over the wired accessnetwork or WLAN connection for wired access networks, either before theuser receives the device or after the user receives the device. In somecases, the device can be connected to general purpose equipment, such asa computer to perform the programming required to complete provisioning.In the cases in which the device is provisioned at point of sale orafter point of sale, the device provisioning can be triggered by a userinitiated sequence, or can be initiated by an automated backgroundsequence at any time after the device is powered on. In such cases, insome embodiments, partial credentials that include information such asdevice type, OEM or service provider are used to assist in determininghow to complete the provisioning, and the information can also includesecure information, certificate or signature programmed into the partialcredentials that is required for the network to perform the provisioningof the remaining credential information in the device and possibly thenetwork. In some embodiments, any network information used/required toprovision the device or service is generated at the time the partialcredentials are determined rather than beforehand.

In some embodiments, the device is activated for service before the userobtains the device with permanent credentials, temporary credentials orpartial credentials, or with a permanent service account or a temporaryservice account. For example, in this case, the necessary steps ofprovisioning and activating service for the device can occur duringmanufacture, at some point in the device distribution, such as at adistribution depot or in a store, or at the point of sale or point ofshipment. In some embodiments, the steps for activating service includeone or more of the following: provision the device (e.g., withpermanent, temporary or partial credentials), provision the necessarynetwork databases and equipment to prepare them to recognize the deviceand associate it with the service profile and/or service plan, create orselect the service account (e.g., permanent or temporary serviceaccount), select or create the service profile and/or service plan,program any elements in the device required to activate service (e.g.,account ID, device aspects of the service profile and/or service plan),and program the necessary network databases and equipment with therequired associations of device credentials and service profile and/orservice plan policy settings. In some embodiments, the device orientedprogramming portions of the service activation steps occur at the sametime, before or after the network oriented programming portions of theservice activation steps.

In some embodiments, the device activation information is programmedwith dedicated apparatus that connects to the device via a wireless orwire line connection. For example, the dedicated apparatus can be localto the location where the device is being provisioned, or the dedicatedapparatus can be partially or entirely networked into a database orservice activation solution located elsewhere and operated by thecentral provider, a VSP, OEM or other entity. For example, the apparatusto program the network portions of the activation information can alsobe networked and the operators who set up the required networkprogramming for a device or group of devices can be in the vicinity ofthe servers that host the service activation and management tools orthey can network into the servers. In some embodiments, activationserver tools operators have full or partial control of any deviceactivation apparatus associated with the entity they work for (e.g.,OEM, VSP or master agent) but only have remote and partial access viasecure terminal, secure website or other techniques to network into thenetwork portion of the activation tools that are controlled by thecentral provider or VSP. The server tools operators can be restricted insome embodiments to providing network activation information or settingsonly for those devices or device groups that are assigned to the entitythey work for with (e.g., OEM, VSP or master agent). For example, thedevice control group restriction can be accomplished with a securedatabase that has secure sub-partitions for one or more entities so thatthey cannot impact the control of one another's network activationsettings but can control their own devices. In this way, a centralizedset of activation tools resources controlled by a central provider, VSPor other entity can be partitioned so that different entities can havepartial or full control of the activation service definition for devicesor groups of devices without impact or risk to others who share thenetwork and activation tools resources.

In some embodiments, activation is accomplished with an over the airinterface to a mobile device, or over the wired access network or WLANconnection for wired access networks, either before the user receivesthe device or after the user receives the device. In some cases, thedevice can be connected to general purpose equipment such as a computerto perform the programming required to complete activation. In the casesin which the device is activated at point of sale or after point ofsale, the final device activation process can be triggered by a userinitiated sequence, or can be initiated by an automated backgroundsequence at any time after the device is powered on. In such cases, someembodiments call for a temporary service account that is used to bringthe device onto the network before the user has input the informationnecessary to create a permanent service account. In some embodiments, atemporary or permanent service account can be applied to the device atthe time the device reaches the network, and the type of account,service profile and/or service plan can be influenced (e.g., partiallydetermined or informed) or determined by information embedded in thedevice credentials or partial credentials, such as device type, deviceID, SIM, OEM or service provider. For example, the device credentialscan also include secure information, certificate or signature that canbe required by the network to perform the activation steps for temporaryor permanent service account status. In some embodiments, in which thedevice is activated in this manner before the user information isavailable, or before the user has selected a pay for service plan, theservice profile and service plan are set up for ambient services asdescribed herein.

In some embodiments, the device is activated during the manufacturing ordistribution process, and then the activated device status is suspended.Once the temporary or permanent service account is set up, withappropriate service profile and/or service plan and temporary orpermanent credentials, in some networks and billing systems the servicecan often be more easily resumed once suspended as compared toprovisioning and activating the device from scratch. The device is thenlater resumed (or re-activated) when some event triggers the resumeprocess, such as when it ships to the end user or when the end userattempts to use it. This process prevents the network from needing tomanage credentials and accounts for devices that have been activated butare not yet on the network.

In some embodiments, provisioning is accomplished at least in part withtemporary credentials in a manner which is automated and convenient forthe user or device owner. In some embodiments, at least some subset ofthe temporary credential elements replaced at a later point in time bypermanent credential elements in a manner that is also automated andconvenient for the user or device owner. In some embodiments, thetemporary credential set is pre-programmed into the device along with atemporary or permanent service account including service profile duringthe manufacturing or distribution process so that the device isactivated with temporary credentials when it ships. In some embodiments,the aforementioned pre-programming is performed for the network via asecure set of server access equipment that networks into the networkdatabases used to define the service profile and/or the service plan. Insome embodiments, a subset of the temporary credentials is recycled onceit is replaced, if a temporary service account is not activated or usedafter some period of time, if a permanent account is not activated orused after some period of time, or if the credentials subset is revokedfrom the device for some other reason.

In some embodiments, more than one device is assigned one or moreelements of the temporary credentials, such as the phone number, whichmay be limited in supply. In some embodiments, a network will acceptmore than one set of temporary credentials, one or more redundantelements, for two or more different devices. In some embodiments, adevice that has two or more temporary credential sets, in which at leasta subset of the credential elements are different for the sets, so thatif one set of credentials has elements that are already being used toaccess the network, then one or more reserve sets can be drawn upon togain access to the network.

In some embodiments, the temporary credentials are used to log onto thenetwork to conduct an over the air or over the network activationprocess in which an activation server reads at least a portion thedevice credentials to determine some aspect of how the device serviceprofile. In some embodiments, the aforementioned over the air activationprocess is accomplished in the background without user intervention. Insome embodiments, the over the air activation process is initiated whenthe user first attempts to use the device or when the user firstattempts to access the network or upon user request or approval. In someembodiments, the over the air activation process is initiated using atemporary service account for the device and/or network to gain accessto the network. In some embodiments, the over the air activation processis initiated after the user has entered the information required tocreate a permanent user account into the device or into the network. Insome embodiments, the user is required to enter the aforementioned userinformation before using the device or using some aspect of the device.In some embodiments, the temporary service account is replaced by apermanent service account some time after the user has entered thenecessary information to create a permanent account into the device ornetwork. In some embodiments, the over the air activation process isinitiated using a permanent service account assignment for the deviceand/or network to gain access to the network.

In some embodiments, the service profile is assigned to the deviceand/or network during the aforementioned over the air activation to be apay for service profile with a free trial period. In some embodiments,the service profile assigned to the device and/or network during theaforementioned over the air activation includes pre-pay, post-pay,session based pay or pay as you go options for service. As will beapparent to one of ordinary skill in the art, various embodimentsdisclosed herein are particularly well suited for control or pre-payservices. In some embodiments, the service profile that is assigned tothe device and/or network during the aforementioned over the airactivation is an ambient service profile providing service access beforeall the user information is available to assign a permanent account. Insome embodiments, the service profile that is assigned to the deviceand/or network during the aforementioned activation is an ambientservice profile providing a service upgrade selection option interfaceto the user. In some embodiments, the service profile that is assignedto the device and/or network during the aforementioned activation is anambient service profile providing transaction services to the user. Insome embodiments, the service profile that is assigned to the deviceand/or network during the aforementioned activation is an ambientservice profile providing bill by account functionality for the network.In some embodiments, the service profile that is assigned to the deviceand/or network during the aforementioned activation is an ambientservice profile providing some amount of free networking or informationservice to entice the user to use the other ambient services. In someembodiments, the aforementioned ambient service is at least partiallyimplemented with device based service activity control or controlassistance. In some embodiments, the aforementioned ambient service isat least partially implemented by gateways, routers or switches in thenetwork that are programmed according to the ambient access profile forthe device to implement the ambient policies for network access control,routing control, traffic control or service monitoring and reporting forbill by account.

In some embodiments, activation is accomplished at least in part with atemporary service account in a manner that is automated and convenientfor the user or device owner. In some embodiments, at least some subsetof the temporary service account is replaced at a later point in time bypermanent service account subset in a manner that is also automated andconvenient for the user or device owner. In some embodiments, thetemporary service account settings (e.g., including the service profilesettings and/or the service plan settings) are pre-programmed into thedevice along with a temporary or permanent credentials set during themanufacturing or distribution process so that the device is activatedwith temporary credentials when it ships. In some embodiments, theaforementioned pre-programming for the network is performed via a secureset of server access equipment that networks into the network databasesused to define the service profile and/or the service plan. In someembodiments, the device is suspended once it is activated but before theuser is using it, and then resumed before or commensurate with the pointin time that the user begins to use it. In some embodiments, some subsetof the temporary service account is recycled once it is replaced, if thetemporary service account is not used after some period of time, if thetemporary service account is not upgraded to a permanent service accountafter some period of time, or if the activation is revoked from thedevice for some other reason. In some embodiments, more than one deviceis assigned to the same temporary service account. In some embodiments,a network accepts more than one device on the same temporary serviceaccount. In some embodiments, a device includes or is associated withtwo or more temporary service accounts, in which at least a subset ofthe temporary service account elements are different, so that if oneaccount is already being used to access the network then one or morereserve accounts can be drawn upon to gain access to the network. Insome embodiments, the temporary service account is associated with atemporary credentials set. In some embodiments, the temporary serviceaccount is associated with a permanent credentials set.

In some embodiments, un-activated devices are detected by the networkrouting equipment (e.g., service gateways or routers in hierarchicalnetworks or base stations with embedded gateways in flat networks) andthe device routing is programmed to re-direct un-activated devices to anactivation server network destination. For example, the activationserver can first inspect the information associated with the device todetermine if the device belongs to the list of devices, device types ordevice groups that the network is programmed to provide access to. Forexample, the information used to determine this can include device type,service provider, phone number, device ID, SIM ID or configuration,secure information used to qualify the device, IP address, MAC address,user, user group, VSP, OEM, device distributor, service distributor(master agent), service processor presence or configuration, presence orconfiguration of other software or hardware. There can also be someactivation definition information embedded in the credentials, orassociated with some portion of the credentials, or programmedadditionally on the device that informs the activation server as to theservice profile and/or service plan and/or service account that shouldbe established for the device. If activation information (the serviceprofile, service plan and/or service account information) is foundthrough association with the device credentials (e.g., device ID, phonenumber, IP address, MAC address, SIM or other security credentials)rather than being read directly from information embedded in the deviceor device credentials, then the pertinent aspects of the credentials canbe used as a cross reference to look up the service plan and/or serviceprofile information stored in a database networked to or within theactivation server. The activation information can include information todefine a wide variety of service plans and service profiles that whenproperly implemented on the network functions, and perhaps device ifnecessary, can provide for a wide range of service activity policies,service billing policies, transaction billing policies and serviceaccount types that can be associated with the device over the air orover the network.

In some embodiments, once the activation server has determined theactivation information from the device or from a look up based on someaspect of the device credentials, then the activation server initiatesthe necessary network settings and billing database entries to beprogrammed by sending the service profile instructions to the networkprovisioning and activation apparatus and the service plan instructionsto the billing system. In some embodiments, the activation server canthen also send the any necessary service profile and/or service plansettings required for the device to a provisioning and activationsupport software function on the device, such as various embodiments ofthe service processor, so that the device provisioning and activationcan be completed. The provisioning can be with permanent credentials ortemporary credentials, and the service account that is set up may bepermanent or temporary. In some embodiments, the activation processdescribed above is completed perhaps before the user has entered some orall of the user information necessary to set up a permanent serviceaccount, and, in these cases, a temporary service account can be set up.In some cases, the activation process can be completed in the backgroundbefore the user has completed an attempt to access the network and theservice profile can be set up to provide ambient services to a temporaryservice account. In some embodiments, the user is required to enter theinformation required to establish a permanent service account prior togaining full use of the device, either on the device, on a computer orin the store, so that by the time the user begins using the device theabove activation embodiments can provide for ambient services activationwith permanent account status so that the user can purchase a serviceupgrade or any transaction without entering any more accountinformation.

In some embodiments, a device status is changed from a temporary serviceaccount to a permanent service account. If the device is activated witha temporary service account, and the user information is available toset up a permanent account, then if the billing system rules andinterfaces allow for such, the user information can be changed from themock information to the actual user information while maintaining thesame account identifiers in the billing system. If the billing systemwill not allow for such, then the user information can be used toestablish a new account, the device credentials can be re-associatedwith the new account, in some cases, after modifying one or more of thedevice credential parameters, and the network functions can bere-programmed as required, and, in some cases, the device can bere-programmed as required to accommodate the new permanent account.

In some embodiments, code on the device pulls a temporary or permanentset of credentials. When the credentials are pulled, the networkassociates the device with an ambient service profile according to oneor more of the following: embedded device information identifying devicetype, service owner (e.g., VSP), user group, or user, or device ID iscross referenced to a database that is populated some time frommanufacturing time to post sale where the database provides informationidentifying device type, service owner (e.g., VSP), user group, or user.The device is then re-directed accordingly (e.g., for device based thisis a matter of setting the policies or loading the software for theservice processor, for the network based approach this is a matter ofpopulating the routing tables and service profile). For example,credentials can be re-cycled after a period of time, and/or some portionof the credentials can be redundant with other devices. For example,this is essentially a dynamic service for (temporarily) assigning devicecredentials, and the duration of the temporary credential validity forthat device ID can be time limited to give the user time to activate areal account or a free trial, session limited, or a longer duration oftime that is perhaps refreshed each time the device logs on. Forexample, the device could also already have permanent or temporarycredentials but not have a service account. The above process can beused to assign a temporary or permanent service account as well. Oncethe service account is assigned and the appropriate service profile ispropagated to the network elements, the device can then be directed toor use the appropriate activation profile service activities or theappropriate ambient service activities.

In some embodiments, the device is activated in the background in amanner that is virtually transparent to the user. For example, at somepoint in the distribution channel, the device is programmed to seek theactivation server system described above as soon as it is turned on, oras soon as some other event occurs like the user using the device or theuser attempting to gain access. When the pre-programmed event istriggered, the device connects to the network and the gateways orrouters re-direct the device to an activation server, as discussedabove. As also described herein, the activation server either derivesinformation from the device that informs the server what service thedevice should be activated with, or the server derives that informationfrom a database look up with a portion of the device credentials as thecross reference parameter. Once the activation server has determined theactivation information from the device or from a look up based on someaspect of the device credentials, then the activation server causes allthe necessary network settings and billing database entries to beconfigured/programmed by sending the service profile instructions to thenetwork provisioning and activation apparatus and the service planinstructions to the billing system. In some embodiments, the activationserver can then also send the any necessary service profile and/orservice plan settings required for the device to a provisioning andactivation support software function on the device, such as variousembodiments of the service processor, so that the device provisioningand activation can be completed. For example, the provisioning can bewith permanent credentials or temporary credentials, and the serviceaccount that is set up can be permanent or temporary.

In some embodiments, background activation is performed using theaforementioned activate/suspend process. At some point in thedistribution channel, the device is programmed to seek to resume serviceas soon as it is turned on, or as soon as some other event occurs likethe user using the device or the user attempting to gain access. Whenthe pre-programmed event is triggered, the device attempts to connect tothe network and the gateways or routers re-direct the device to anactivation server as described herein. As also described herein, theactivation server either derives information from the device thatinforms the server that the device is ready to resume service, or theserver derives that information from a database look up with a portionof the device credentials as the cross reference parameter. Once theserver is aware of this information, it sends a message to resumeservice to the billing system, or other network function that controlsthe suspend/resume function, and the service is resumed.

In some embodiments, background activation is performed as describedbelow. The service processor and the credentials are pre-programmedduring the manufacturing or distribution process to provide the desiredservice profile support and/or billing profile support for the desiredinitial ambient service. As described herein, this programming can beaccomplished with dedicated apparatus at the manufacturer ordistribution depot. Furthermore, the party responsible for defining theservice (e.g., typically the central provider, OEM, VSP, distributor ormaster agent) can network into the service processor programmingapparatus to control service processor and/or credential programming forall or a subset or group of the devices or device types locallyavailable. The service processor enabled device is programmed to seekthe activation server system described above as soon as it is turned on,or as soon as some other event occurs like the user using the device orthe user attempting to gain access. In some embodiments, the activationserver is the access control server previously discussed or the accesscontrol server can act in concert with another server that performs theactivation function. When the pre-programmed event is triggered, thedevice connects to the network and the gateways or routers re-direct thedevice to the activation server. As also described herein, theactivation server can communicate with the service processor to verifythe service processor security credentials, agents and configuration.

In some embodiments, if the activation server determines that thepre-programmed settings stored in the service processor need to bemodified to provide the latest version of the desired service, or if theservice processor agent software needs to be updated, then this can beaccomplished prior to completing the activation process. Once theservice processor configuration and settings are confirmed, theactivation server causes the necessary network settings and billingdatabase entries to be programmed by sending the service profileinstructions to the network provisioning and activation apparatus andthe service plan instructions to the billing system. Given that theservice processor can perform some or much of the service activitycontrol or control assistance, the service control options are generallylarger than without the service processor, and there can be lessconfiguration to perform for other networking equipment to complete theprovisioning and activation process. The provisioning can be withpermanent credentials or temporary credentials, and the service accountthat is set up can be permanent or temporary.

In some embodiments, pre-programming and pre-activation of devices withtemporary credentials and a temporary service account are used to shipdevices that are pre-activated. Given that the credentials are temporaryand can be recycled when the permanent credentials are assigned,concerns about using up too many pre-assigned credentials are reduced.In embodiments in which a portion of credentials elements can be usedfor multiple devices, this concern is further reduced. If there is aconcern about too many activated devices being assigned that are notactually active and generating service revenue, then the suspend/resumeprocess discussed herein can be employed. In some embodiments, thetemporary credentials and/or temporary account can be replaced withpermanent credentials and/or account assignments at any time as follows.When a pre-programmed event in the device is triggered, then the deviceinitiates a program that seeks the aforementioned activation server oranother server that has the capability of fulfilling the device requestto exchange the temporary credentials for permanent credentials and/orexchange the temporary account for a permanent account. The event thattriggers the credential exchange can be the same or different than theevent that triggers the service account exchange. The service accountexchange can typically be triggered by the point in time that the userenters account information.

In some embodiments, the aforementioned ambient service is partlyimplemented with a combination of the techniques for pre-provisioningduring manufacturing or distribution and at least partially implementingthe service activity control (e.g., access control, routing policy,traffic control, usage limits, and/or policy for usage limit overage)required for implementing ambient using the service policy provisioningcapabilities in the data path gateways, routers or switches in thenetwork. The gateways, router or switches are pre-programmed asdiscussed herein according to the ambient access profile for the deviceto implement the ambient policies for network access control, routingcontrol, traffic control or service monitoring and reporting for bill byaccount. In some embodiments, the provisioning credential elements arenot all pre-programmed before the device ships, but a subset of thecredential elements are programmed using the activation server techniquediscussed herein. This over the air automated provisioning is combinedwith the activation server reading the device credentials to derive theservice activity control settings for the gateways, routers or switchesthat will result in the desired ambient services activity controls.

In some embodiments, the aforementioned ambient service is implementedwith a combination of the techniques for pre-activation duringmanufacturing or distribution and at least partially implementing theservice activity control (e.g., access control, routing policy, trafficcontrol, usage limits, and/or policy for usage limit overage) requiredfor implementing ambient using the service policy control capabilitiesin the data path gateways, routers or switches in the network. Thegateways, router or switches are programmed to recognize thepre-activated device credentials as discussed herein according to theambient access profile for the device to implement the ambient policiesfor network access control, routing control, traffic control or servicemonitoring and reporting for bill by account. In some embodiments, thedevice activation profile and/or service account are not pre-programmedin the network and/or the device before the device ships but theactivation profile and/or service account are programmed using theactivation server technique discussed herein. This over the airautomated provisioning is combined with the activation server readingthe device credentials to derive the service profile activity controlsettings for the gateways, routers or switches that results in thedesired ambient services activity controls.

In some embodiment, a VSP capability is enabled by providing a securenetwork connection to the service policy settings tools that define thedevice pre-provisioning settings, the device pre-activation serviceprofile settings, the network equipment service activity control policysettings (e.g., access control, routing policy, traffic control, usagelimits, and/or policy for usage limit overage), and the network billingsystem database. By providing server tools that enable all thesesettings to be controlled (or perhaps only observed in the case of thebilling system) by a secure workstation or secure website interface thatnetworks into the equipment that programs the settings, and providingfor a secure partitioning of the devices that can be controlled by agiven secure workstation or secure website interface, a central providercan provide VSP services to multiple entities who all have differentdevice and service plan combinations that they desire different flavorsof ambient services for. These techniques can also be extended beyondambient to any device/service profile/service plan combo the VSP desiresto create. In some embodiments, the networking equipment is implementedto secure device service group domains in which the service policies fora group of devices can be controlled. In some embodiments, thepre-provisioning and pre-activation techniques are substituted with theover the air activation server techniques discussed herein, and a securedevice group partition capability is provided in the activation serveras well so that the activation server device group partition controlcapabilities can be added to the secure device group partition controlcapabilities of the network gateways, routers and/or switches, thedevice programming tools and the billing system to form a VSP partitionsolution for over the air activation of various device/service plancombinations. In some embodiments, the device groups are relativelysmall so that beta trials of arbitrarily large or small size can bedesigned and implemented by defining a service control group asdescribed above, and after fine tuning and perfecting the beta trialsettings the device group can be expanded to publish the automatedprovisioning and activation service settings to a larger user or devicegroup for production services.

In some embodiments, device based service activity control assistance(e.g., based on the various service processor embodiments describedherein) is combined with simplified provisioning techniques describedherein so that service processor enabled devices can be shipped withpre-provisioned credentials (temporary or permanent) or can obtaincredentials in an automated manner that is convenient and efficient forthe user or device owner. In some embodiments, the service processorembodiments in combination with the manufacturing and supply chaincredentials and provisioning apparatus described elsewhere providevarious approaches for provisioning pre-provisioned service processorenabled devices. In some embodiments, the service processor embodimentsin combination with the activation server variants discussed aboveprovide various approaches for over the air or over the networksimplified post-sale provisioning for service processor enabled devices.For example, these embodiments can also be used for ambient servicesgiven that as discussed herein the service processor has capability toimplement service profile policies for deep control of ambient serviceactivity control.

In some embodiments, provisioning includes provisioning partial devicecredentials that include, for example, a secure certificate that is usedto authorize full credential provisioning and/or activation byperforming a process for a later look-up/validation of the full devicecredentials. For example, the look-up/validation of the full devicecredentials can be performed by a gateway, router or similar networkdevice that re-directs to a provisioning server and/or activation serveror other network components that either: (1) recognizes the partialcredentials that serve as a reference to direct the device communicationto a specific provisioning/activation server determined from the partialcredentials; or (2) does not recognize the partial credentials, anddirects the device communication to a less specificprovisioning/activation server that is not necessarily associated with areference to the partial credentials.

In some embodiments, if the partial device credentials (e.g., temporaryor permanent credentials) are being used for provisioning, then thepartial credentials are read (e.g., and/or other credentials can belooked up based on the partial credentials as described above). Thedevice is authorized if the proper credentials and/or secure certificateis present. The device credential provisioning is then completed (e.g.,using activation server commands or settings to a device based softwareand/or hardware element), and the credentials are, in some cases, alsocommunicated to the various network equipment elements.

In some embodiments, if the partial device credentials are being usedfor activation, then partial or full device credential provisioning isperformed, such as described above. A service account (e.g., temporaryor permanent service account) is created or looked up based on thepartial device credentials (e.g., a user account associated with thedevice through embedded partial or full credentials or a look upprocess, or based on a dynamically created/assigned temporary accountassociated with the device through embedded partial or fullcredentials). An initial service profile and, in some cases, an initialservice plan (e.g., service control policy settings including a billingprofile) are determined from embedded information and/or using a look upprocess (e.g., based on the device type and/or partial or full devicecredentials). The device is then programmed to enable access with theservice profile and plan, and, in some cases, the various networkcomponents/elements are programmed to enable the service profile andplan, and, in some cases, proper entries in the billing system are madeor confirmed, and the device credentials are, thus, activated forservice.

In some embodiments, the above described provisioning and/or activationprocesses are performed with the provisioning server(s) and/oractivation server(s) in the background with reduced, minimal or no userinput required, for example, after the device is sold to the user andthe user turns on the device so that by the time the user attempts toaccess the service using the device, the provisioning and/or activationprocess is already completed.

In some embodiments, device based service activity control assistance(e.g., based on the service processor embodiments) is combined withsimplified activation techniques described herein so that serviceprocessor enabled devices can be shipped with pre-activated accounts(temporary or permanent), or can obtain activated account status in anautomated manner that is convenient and efficient for the user or deviceowner. In some embodiments, the service processor embodiments incombination with the manufacturing and supply chain activation andprovisioning apparatus described elsewhere provide various approachesfor pre-activated service processor enabled devices. In someembodiments, the service processor embodiments in combination with theactivation server variants discussed above provide various approachesfor over the air or over the network simplified post-sale accountactivation for service processor enabled devices. These embodiments canalso be used for ambient services given that as discussed herein theservice processor has capability to implement service profile policiesfor deep control of ambient service activity control.

As discussed herein, in some embodiments for activation, the network AAA(or other network function) either recognizes one or more aspects of apre-activated device credentials and routes the pre-activated devicecommunication to an activation server that is appropriate for thatdevice (routing information either derived through look up of thecredential aspect or by obtaining the required information directly fromthe credential itself), or the AAA (or other network function) does notrecognize the credentials and routes the device communication to anactivation server for unrecognized device credentials. In either case,in some embodiments, one or more of the credential aspects can then beused to perform a secondary determination of what provisioning and/oractivation sequence to perform in association with the device, or whichactivation server sequence the device should be directed to. Forexample, one or more device credential aspects can be read and used as across-reference to determine a routing for the device communication (orthe information required for routing can be in the device credentialinformation itself) so that the device can be routed to the appropriateactivation server sequence.

In some embodiments, an activation server sequence can be determined atleast in part by using a browser server or a portal (e.g., http server,https server, WAP server or another standard or custom protocol serverfor a browser, embedded or automated browser or a portal client in thedevice). In some embodiments, the browser server is an http or httpsserver. The pre-activated device communication can be routed to thehttps server in a manner similar to that described above, and the servercan read the information embedded in the https communication todetermine the device credential information required to initiate thecorrect provisioning completion and/or activation sequences. Forexample, the https header information, tokens, cookies or other secureinformation communicated over https from a secure embedded client on thedevice (or user) can either provide the activation server with theinformation required to perform the cross-reference to an appropriateprovisioning and/or activation sequence, or the https embeddedinformation or the embedded client (or user) information can instructthe activation server on which services the device is to be provisionedand/or activated on and any necessary device or user information (e.g.,device owner and/or billing information) can be exchanged, or the devicemight be provisioned and/or activated first on a free ambient servicewith temporary or permanent credentials or account.

In some embodiments, the service processor can be combined with thepre-provisioning and pre-activation techniques described above to createan ambient service solution that will work on roaming networks in whichthe central provider or VSP has no control or minimal control over thenetwork elements. For example, the device includes a service processorpre-programmed for ambient service activity control as discussed herein,and the device credentials and other settings are pre-provisioned andpre-activated for the central provider network, all of which isdescribed in numerous embodiments disclosed herein. Provided that theservice provider has a roaming agreement with other service providers,or provided that the device may gain access to the roaming network, whenthe device is roaming it will be capable of ambient connectivity withbill by account functionality and all the other features of ambient.Furthermore, as also discussed herein, the ambient service activitycontrol policies can be different for different roaming networks toaccommodate the varying network costs and performance. Also, forexample, it would be permissible to sign up for initial services oradditional upgrade services with the central provider while roaming onthe roaming partner network. One of ordinary skill in the art willappreciate that this also allows for creating a VSP or MVNO for thepurpose of creating a clearing house for central provider serviceactivations according to geography or user choice. By using a globalmulti-mode modem module, and maintaining service agreements with amultitude of carriers, the MVNO or VSP can provide consistent ambientservices across multiple carriers and multiple geographies while stillmaintaining a good degree of cost control. Using bill by accountcapabilities, it is also possible to have an activation agreement wherea roaming service provider agrees to refund the cost of ambient roaming.From the ambient service platform, the VSP or MVNO can then provideservice purchase options to the user based on the carrier networksavailable to the device, or the VSP or MVNO can broker the user off toany of the carriers by activating the device onto the carriers maincentral provider service.

Accordingly, these embodiments provide flexible capabilities foractivating a device or group of devices with a broad range of serviceprofiles and service plans by simply programming the device with theproper credentials at some time during manufacturing or distribution, orsimply programming a database associated with the network so that aportion of the device credentials can be used to look up the desiredservice profile and service plan. For example, various activationembodiments described herein are highly convenient for the end user andneed not, in many cases, involve any human intervention.

The service processor 115, service controller 122, policy implementationand/or profile implementation and various embodiments disclosed hereinare applicable to conventional communication products as well as machineto machine applications. For example, if the machine to machine deviceincludes a service processor 115 with an activated account, then theservice profile settings can be optimized for machine communications toprovide only the limited access required to support the particularmachine to machine application. This allows for cost optimized accessservices and prevents the machine to machine device or access modem frombeing misappropriated and used for some other service access than thatintended. For example, by programming the machine to machinecommunications device at time of manufacture or during distribution withcredentials or partial credentials that provide for automatedprovisioning and activation as described herein, the device can beautomatically provisioned and activated on the service network with aservice account when deployed, thus eliminating the need for costly ortime consuming human intervention. The various embodiments that make itsimpler to design, manufacture, test and deploy devices may also beequally applied to machine to machine devices. These embodiments includethe service processor 115 developers kit and the automated provisioningand activation management tools among others. Also, the service analysisand test tools and the virtual service provider embodiments can also beapplied to machine to machine applications.

FIG. 1 illustrates a wireless network architecture for providing deviceassisted services (DAS) install techniques in accordance with someembodiments. As shown, FIG. 1 includes various wireless communicationsdevices 100 (e.g., a mobile wireless device or an intermediatenetworking device) in wireless communication with central provideraccess and core networks 210. As shown, some of the devices 100 includeservice processors 115. For example, devices 100 can include varioustypes of mobile phones, PDAs, computing devices, laptops, netbooks,tablets, cameras, music/media players, GPS devices, networkedappliances, and any other networked device. In some embodiments,intermediate networking devices, as described herein, include a serviceprocessor or assist in the downloading of a service processor for one ormore devices 100 to facilitate network access as described herein withrespect to various embodiments. In some embodiments, a device 100 doesnot initially include a service processor (as shown in FIG. 1). In someembodiments, a service processor 115 is previously installed (e.g.,during manufacture or distribution), or is downloaded and installed on adevice 100 (as also shown in FIG. 1).

In some embodiments, the wireless communications device is a mobilecommunications device, and the service includes one or more Internetbased services, and the mobile communications device includes one ormore of the following: a mobile phone, a PDA, an eBook reader, a musicdevice, an entertainment/gaming device, a computer, laptop, a netbook, atablet, and a home networking system. In some embodiments, the wirelesscommunications device includes a modem, and the processor is located inthe modem. In some embodiments, an intermediate networking deviceincludes any type of networking device capable of communicating with adevice and a network, including a wireless network, example intermediatenetworking devices include a femto cell, or any network communicationdevice that translates the wireless data received from the device to anetwork, such as an access network. In some embodiments, intermediatenetworking devices include 3G/4G WWAN to WLAN bridges/routers/gateways,femto cells, DOCSIS modems, DSL modems, remote access/backup routers,and other intermediate network devices.

In some embodiments, there are at least two versions of a serviceprocessor. For example, a first version service processor can be ageneric version of a service processor version that can be pre-installedduring manufacture or distribution and used for downloading a secondversion service processor. For example, the first version serviceprocessor can be a generic version that is not specific to a devicegroup while the second version is specific to a device group. As anotherexample, the first version service processor installed during time ofmanufacture or during device distribution may not contain all of thefunctions that are available for a permanent second version serviceprocessor that is installed when the device first connects to a network.As another example, service processors can be regularly updated tochange the security parameters of the software, such as softwaresignatures, encryption, obfuscation, secure query response sequenceinformation, and/or other parameters, so that it becomes more difficultto hack or otherwise modify the software. As another example, the secondversion service processor can be uniquely associated with the device 100(e.g., wireless communications device or an intermediate networkingdevice) and the associated service plan and/or service provider. In someembodiments, a first version service processor is installed on a device100 (e.g., service processor 115 installed on the device 100 can be afirst version service processor that was previously installed duringmanufacture or distribution, or downloaded and installed during initialnetwork access, as shown in FIG. 1). In some embodiments, a secondversion service processor is installed on a mobile device (e.g., serviceprocessor 115 can be a second version service processor that waspreviously installed during manufacture or distribution, or downloadedand installed during initial network access, as shown in FIG. 1).

In some embodiments, a new and/or updated version service processor 115can be downloaded from, for example, a service processor download 170,as described herein. In some embodiments, the service processor download170 provides a function or service that is located elsewhere in thenetwork or partially located in elsewhere or integrated with/as part ofother network elements (e.g., the service processor download 170 can bea function/service of service control 150 and/or service policies andaccounting 165). In some embodiments, the devices 100 are in servicecontrol communication with service control 150 via central provideraccess and core networks 220 as shown in FIG. 1. Service policies andaccounting functions 165 are also provided in communication with thecentral provider access and core networks 220 as shown in FIG. 1. Insome embodiments, the service policies and accounting functions 165provides a function or service that is located elsewhere in the networkor partially located in elsewhere or integrated with/as part of othernetwork elements (e.g., the service policies and accounting functions165 can be a function/service of service control 150).

In some embodiments, the devices 100 network access is initiallyrestricted to service control related access for service processor 115verification and/or download(s)/update(s) (e.g., a first version serviceprocessor installed on the mobile device 100 can limit or direct networkaccess to the service control 150, service processor download 170,and/or service policies and accounting function 165), as describedherein with respect to various embodiments. In some embodiments, afterthis initial restricted access period is completed and/or if the serviceprocessor 115 of the mobile device 100 is verified for the device and iscurrent/updated, the device 100 can communicate via the central provideraccess and core networks 220 to the Internet 120 for access to variousInternet sites and/or services 240 as shown in FIG. 1 (e.g., Googlesites/services, Yahoo sites/services, Blackberry services, Apple iTunesand AppStore, Amazon.com, FaceBook, and/or any other Internet basedsites and/or services) based on, for example, the service planassociated with the device 100. In some embodiments, service usageinformation (e.g., based on network based CDRs or device generated CDRs,such as micro-CDRs generated by the service processor 115, and/or otherservice usage measures) are used for service control and/or service planbilling and reporting, as described herein with respect to variousembodiments.

Those of ordinary skill in the art will appreciate that various othernetwork architectures can be used for DAS install techniques, and FIG. 1is illustrative of just another such example network architecture forwhich DAS install techniques described herein can be provided.

In some embodiments, FIG. 1 provides a wireless network architecturethat also supports partitioned device groups, in which each device groupcan be provided independent and secure management. In some embodiments,partitioned device groups are provided. In some embodiments, eachpartitioned group of devices (e.g., mobile devices 100) can be uniquelymanaged with secure admin log-ins. In some embodiments, the partitioneddevice groups are securely managed using the service processor 115installed on the devices 100 for that device group. In some embodiments,multi-device, multi-user accounting is provided. In some embodiments,capabilities are provided to support multi-party/multi-servicereconciliation records to carriers and carrier partners. In someembodiments, service usage and profitability analytics are provided. Forexample, a partitioned beta test group of devices can be tested andoptimized for various service usage policies and/or service plans, andthen the optimized service usage policies and/or service plans can bepublished to an entire or larger device group. In some embodiments, acarrier can be provided a carrier branded device group, and/or a MVNOcan be provided a MVNO branded device group.

In some embodiments, DAS install clients (e.g., bootstrappers fordevices 100) are provided. In some embodiments, a first version serviceprocessor provides DAS install client function that facilitates abootstrapping function for downloading and installing a second versionservice processor. In some embodiments, DAS install clients are providedfor creating/downloading and installing a verifiable service processorfor each device (e.g., a network capable device, such as a mobilewireless communications device or intermediate networking device). Insome embodiments, a DAS install client downloads a uniquely securedservice processer for device 100 (e.g., hashed/encrypted, such as basedon device credentials, to prevent, for example, mass hacking or othersecurity vulnerabilities, and/or a signed interface between the serviceprocessor and modem). In some embodiments, a non-advertised IP addressallocated for each device group is rotated (e.g., to counter denial ofservice (DoS), distributed denial of service (DDS), and/or other typesof attacks and/or vulnerabilities or exploits), and service processorsare configured with multiple IP addresses for service control access(e.g., for secured network communication with service control 150 and/orservice policies and accounting 165).

In some embodiments, DAS install techniques include one or more of thefollowing operations. First, in some embodiments, whether a device is ina device group or list that includes an installed, up to date, and/orvalidated service processor is determined (e.g., verify that SIM, ESN,or other unique device identifier is registered, such as in a HomeLocation Register (HLR)/Network Information Repository (NIR) database orother authorized data store, as associated with servicesettings/policies for that device for service access and send itsassociated Charging Data Records (CDRs) to the service controller).Second, in some embodiments, if the device does not have an installed,up to date, and/or validated service processor, then the device isdirected to, for example, an activation server to, for example,authenticate the device and/or verify a service processor for the device(e.g., ensure that a current and verified service processor version isinstalled and/or download a current and verified service processorversion for the device).

For example, a DAS install client can be downloaded and installed (e.g.,using various bootstrapping techniques, in which, for example, duringthe installation of the service processor software it is sometimesnecessary to update the installer or package manager itself, by using,for example, a small executable file, such as a bootstrapper, thatupdates the installer and then initiates the new/updated/second versionservice processor installation after the update, and, in some cases, thebootstrapper can install other prerequisites for the service processorsoftware during the bootstrapping process as well; and using networkaccess to a download server, and/or from a website, including, forexample, service processor download function 170) that allows for secureconnection from the device (e.g., mobile device 100) to a securedownload server (e.g., service processor download 170). In this example,support for a configuration of the device can be determined, such asthrough a device query or device download of client verificationsoftware can be used to verify the device hardware/softwareconfiguration). In this example, a user/device validation step can alsobe performed. For example, an authorization process for a user sign-upcan be performed (e.g., based on a user name, MAC address, Turingmachine text verification, and/or credit card verification or usingother authorization/validation techniques), in which this can beperformed automatically or the user/device can be required to entercertain credentials for authorization/validation.

In some embodiments, the authorization process also includes varioussecurity techniques for securely associating a user's identity with thedevice (e.g., using public key/TLS techniques, SSH techniques for TLS,and/or identity management techniques or other security techniques). Forexample, a check can also be performed to determine if the device waspreviously and/or is currently an activated device (e.g., the device isalready associated with an active service plan). For example, whetherthe device belongs to a registered device group can also be determinedduring a DAS install, and if not, then the default settings for thattype of device can be applied. In some embodiments, the serviceprocessor is encrypted, hashed, and/or obfuscated based on the previousdetermination (e.g., device group association, default device settings,and/or any other settings/criteria).

In some embodiments, if the device is not associated with a service plan(e.g., based on the device look-up using device based uniqueidentifier(s)/credential(s) or using other techniques, as describedherein), then the device can be redirected to a service portal for anactivation offer for a service plan (e.g., using an activation server).In some embodiments, the portal utilizes header information to indicatethat the device is a managed device (e.g., for a given service provider,MVNO, or other service partner) in the portal request to proxy to anappropriate proxy server for that service provider for the activationprocess.

In some embodiments, the device is in probation mode after the newservice processor install (e.g., restricted a restricted IP address canbe used for the service controller or other network element for servicecontrol instead of the secured service controller IP addresses reservedfor validated and non-probation mode service processors, which, forexample, can reduce the risks of various security risks, such as DoS,DDS, and/or other mass or other types of attacks against publicly orother more easily accessible service controller or download servers). Insome embodiments, while in probation mode, the service processorexecutes more robust service monitoring techniques (e.g., more frequentand/or more robust service integrity checks and/or more frequentheartbeats, for example, to monitor actual device/user behavior with theassociated expected behavior, as described herein with respect tovarious embodiments). In some embodiments, after a probation periodends, the device is provided access based on the associated serviceplan, which is managed, at least in part, by the service processor(e.g., service processor 115) in communication with, for example, aservice controller (e.g., service control 150 and service policies andaccounting 165) or other authorized network elements for servicecontrol.

In some embodiments, the various techniques and embodiments describedherein can be readily applied to intermediate networking devices (e.g.,an intermediate modem or networking device combination). In someembodiments, intermediate networking devices include, for example,WWAN/WLAN bridges, routers and gateways, cell phones with WWAN/WLAN orWWAN/Bluetooth, WWAN/LAN or WWAN/WPAN capabilities, femto cells, back upcards for wired access routers, and/or other intermediate networkingdevices. In some embodiments, an intermediate networking device (e.g.,an intermediate modem or networking device combination) downloads andsends a service processor to one or more devices communicating via theintermediate networking device. In some embodiments, an appropriate andvalidated service processor is securely downloaded to the intermediatenetworking device, and the intermediate networking device performs theservice processor functions for various wireless communication devices(e.g., mobile wireless communication devices) in communication with theintermediate networking device. In some embodiments, in which one ormore wireless communication devices are in wireless communication via anintermediate networking device, some of the service processor functionsare performed on the intermediate networking device (e.g., anappropriate and validated service processor is installed or securelydownloaded and installed on the intermediate networking device), andsome of the service processor functions are performed on the one or morewireless communication devices (e.g., an appropriate and validatedservice processor is installed or securely downloaded and installed onthe mobile device) (e.g., stack controls can be performed on the mobiledevice and various other controls can be performed on the intermediatenetworking device). In some embodiments, the one or more wirelesscommunication devices cannot access the network via the intermediatenetworking device (e.g., the devices are quarantined) unless the one ormore wireless communication devices each have an installed andfunctioning verified service processor (e.g., using CDRs fromintermediate networking device and/or network).

In some embodiments, a USB WLAN stick or other similar networking deviceis provided (e.g., including a modem) with DAS install client softwarethat loads onto the device 100 and installs a service processor 115 onthe device 100. In some embodiments, software on the device 100instructs the user to insert a properly configured memory device (e.g.,a secured USB memory stick, dongle, or other secured device that canprovide a DAS install client software, a service processor image, and/ordevice credentials for network access). In some embodiments, the USBWLAN installed software assumes control over, for example, the networkstack of the device (e.g., for managing network access) and sets variousservice policies based on whether the service is communicated via theUSB WLAN stick or via the WiFi/other (e.g., including requiring nopolicies, such that access is open). In some embodiments, the DASinstall client software on the USB WLAN stick provides a secure clientthat installs itself/certain software on the device that provides a DASinstall client (e.g., bootstrapper) for the device, and the DAS installclient downloads an appropriate service processor onto the device and/orthe USB WLAN stick (e.g., the stack can also be located and managed onthe USB WLAN stick).

In some embodiments, DAS install techniques include ensuring that adevice's (e.g., the device modem's) credentials for the access networkmatch the unique credentials for the service processor and the uniquecredentials for the device (e.g., MAC, SIM, IMSI, and/or other uniquecredentials for the device). In some embodiments, DAS install techniquesinclude ensuring that multiple IP addresses are not associated with thesame service processor for a particular device. In some embodiments, DASinstall techniques include determining that this is the samedevice/modem that a service processor was previously downloaded for andwhether that prior service processor is still active on the network. Ifso, then, in some embodiments, the user is required to type in, forexample, a password to continue, for example, a reimaging of the device(or prevent the new device install or to disable the previouslyactivated other service processor).

In some embodiments, DAS install techniques include starting with adevice that does not include a service processor (e.g., a device, with,for example, a SIM or EVDO ESSN, but with no service processor, attemptsto connect to the network, an appropriate service processor for thedevice is determined, and then a uniquely associated service processoris downloaded and installed on the device, for example, using abootstrapper, as similarly described herein). In some embodiments,unique device credentials (e.g., MAC, SIM, IMSI, and/or other uniquecredentials for the device) are used to create a secure connection with,for example, the service controller (e.g., service control 150) or asecure download server (e.g., service processor download 170), todownload a (e.g., new or replacement) service processor to be securelyinstalled on the device. Accordingly, as similarly described herein, DASinstall techniques can be applied to at least one or more of thefollowing situations: a new service processor install; and/or areplacement service processor install (e.g., the originally/previouslyinstalled service processor was wiped/reimaged, hardware failure, orotherwise corrupted or deleted, and, thus, a replacement serviceprocessor is needed). In some embodiments, when a device connects to thenetwork without, for example, a service processor, then a look up isperformed (e.g., in a data store, such as a database) to determinewhether the device is a member of a device group or a new device, and anappropriate service processor (e.g., version and settings) is providedfor installation on the device. In some embodiments, when the deviceattempts an initial access to the network, at that time an updatedversion of a service processor for that device can be provided based on,for example, device type, device group, master agent, user interface(UI), settings, marketing pages, and/or other features and/or settings,which, for example, can allow for a new, changed, or evolving serviceplan/program by the time the device logs onto the network to provide,for example, for a dynamic and scalable solution.

In some embodiments, as similarly discussed above, two versions of theservice processor are provided (e.g., a first version/image and a secondversion/image of the service processor software). In some embodiments, afirst version service processor is a general purpose version used, forexample, primarily for connecting to the network and loading a secondversion service processor software that, for example, can be one or moreof the following: an updated version, a version tailored to a morespecific purpose (e.g., based on a device type, device group, servicetype, service provider or service provider partner, or any otherpurpose/criteria), a version that includes additionalfeatures/functionality, an encrypted service processor version, aversion that includes special service plan settings or capabilitiesassociated with a device group, a version that includes specificbranding or features/functionality for a given service provider orservice provider partner associated with a device group, a version thatincludes special marketing materials to motivate the user to try or buyservices or transactions associated with a device group, and variousother versions as will now be apparent to one of ordinary skill in theart in view of the various embodiments described herein.

In some embodiments, depending on whether the user has pre-signed up fora service plan, for example, a different version of the serviceprocessor software and/or settings is/are downloaded to the deviceduring this initial service processor download process, including, forexample, one or more of the following: a different set of options forservice plan choices, marketing materials, ambient service settings andservice options, service plan settings, and possibly various otherfeatures and/or settings.

In some embodiments, the first version of the service processor isinstalled during manufacturing or in the distribution channel prior tosale of the device. In some embodiments, the first version of theservice processor is installed after the time of sale of the deviceusing various DAS install techniques as described herein with respect tovarious embodiments.

In some embodiments, the first version of the service processor is notuniquely encrypted so that a general purpose version of the firstservice processor image can be distributed to multiple devices (e.g.,downloadable via the Internet, such as through a website, or a softwareupdate not installed by an operable service processor or a softwareimage that is loaded onto the device before the device credentials ordevice group associations are available or known). In some embodiments,a non-encrypted generic version of the service processor is used forbroad distribution to many devices in which the device credentials arenot known at the time of service processor software distribution (e.g.,the generic version of the service processor can log onto the network toaccess a software update function in the service controller or servicecontrol 150, service processor downloader or service process download170, and/or similar authorized network function, then the servicecontroller can obtain the device credentials and/or user information andprovide an updated version of the service processor using the varioustechniques or similar techniques to those described herein). In someembodiments, the second/updated version of the service processor isuniquely encrypted (e.g., based at least in part on the devicecredentials or device group associations).

In some embodiments, a first version of the service processor need notbe uninstalled and replaced by a new install of a second version of theservice processor, as, in some embodiments, the second version of theservice processor includes updates to the first version of the serviceprocessor, settings changes to the first version of the serviceprocessor, and/or encryption or obfuscation of the first version of theservice processor to provide a second version of the service processorthat is uniquely associated with the device, the device user, the devicegroup, and/or the service plan associated with the device. In someembodiments, the second/updated version of the service processorincludes one or more restricted IP addresses providing for access to thesecured service control/service controller IP addresses reserved forvalidated and non-probation mode service processors, which, for example,can reduce the risks of various security risks for the secured servicecontrol/service controller(s), such as DoS, DDS, and/or other mass orsecurity attacks against publicly or other more easily accessibleservice control/service controller(s) and/or service processor downloadservers.

In some embodiments, the second version of the service processor isuniquely associated with some aspect(s) of the device credentials and/oruser information with a temporary user account (e.g., also sometimesreferred to herein as a dummy user account) or user account. In someembodiments, the second version of the service processor and/or thesettings in the service processor are chosen based on a look up of someaspect of the device credentials and/or the user information todetermine which device group version of the service processor and/orsettings should be loaded. In some embodiments, when there is noappropriate device group association or the user preference takespriority over device group association, the first version of the serviceprocessor software is used to log onto the network (e.g., includingpotentially the service controller) to select a service offer, or devicegroup association that then determines the second version and/orsettings of the service processor software that will be loaded onto thedevice.

In some embodiments, the first version of the service processor isinstalled on aftermarket devices, and after installation this moregeneral purpose version of the service processor provides for access tothe service control/service controller (or similar network function). Insome embodiments, the service control/service controller determines whattype of device and/or what operating system (OS) software and/or whatmodem and modem software is on the device, and then loads an appropriateversion of the service processor for that device or facilitates anupdating of the first version of the service processor to provide asecond version of the service processor for that device.

In some embodiments, the service processor is distributed on aperipheral device suitable for use with more than one type of deviceand/or more than one type of OS. Accordingly, in some embodiments, morethan one version of the service processor can be shipped with the devicefor installation on the device once the device type and/or OS typeis/are known, with each version of the software either being a firstversion of the service processor software as discussed above, or asecond version or final version of the service processor software assimilarly discussed above with respect to various embodiments.

In some embodiments, the first version/second version service processorsoftware techniques, for example, allow for installations of a new OSversion that is not compatible in some way with the present version ofthe service processor. For example, the installation of such a new andincompatible OS version can render the currently installed serviceprocessor version incapable of connecting to the network and updatingthe service processor. In such an example, a first version serviceprocessor software image that is compatible with the new OS can be usedto access the network (e.g., connect to the service control/servicecontroller or some other network element) to download and install a new,possibly uniquely encrypted and compatible second service processorimage, as similarly discussed above with respect to various embodiments.

In some embodiments, the first version/second version service processorsoftware techniques, for example, can handle situations in which adevice has an inadvertently wiped or damaged service processor imagesuch that the device is no longer capable of logging onto the networkwith its secure credentials and/or uniquely encrypted service processorsoftware image. In such an example, the first version software processorcan then be used as similarly described above with respect to variousembodiments to download and install a new/replacement second versionservice processor on the device.

In some embodiments, there are multiple types of device log-in to theservice control/service controller depending on whether a first orsecond version service processor is being used. For example, if a secondversion service processor is being used, which, in some embodiments,includes unique secure credentials, a uniquely encrypted or secureheartbeat channel, and/or a uniquely encrypted service processorsoftware image, then the capabilities of the device and/or serviceprocessor to access the network and/or service controller elements canbe as similarly described herein with respect to various embodiments.However, if the device is using a first version service processor,which, for example, does not have unique secure credentials, a uniquelyencrypted heartbeat control channel, and/or a uniquely encryptedsoftware image, then the heartbeat control channel traffic can behandled in a differential manner as compared to the traffic handlingimplemented for a second version service processor image. For example,the service controller heartbeat processing elements can detect that theservice processor is a first version service processor and can thenroute the heartbeat traffic through a different set of securityprocesses that do not rely on all the security aspects present in asecond version service processor. As another example, the first versionservice processor can be a widely distributed software image that doesnot have unique encryption on the heartbeat channel and can be handleddifferentially, such as handled with a different server designed tohandle insecure traffic and designed to not be disposed or easilyexposed to mass or other security attacks (e.g., DoS, DDS attacks, andother types of security related and/or mass/large scale attacks againsta network element, such as a download server or web/application server).

In some embodiments, a device supports two or more operating systems(e.g., different versions of operating systems and/or differentoperating systems) and for each operating system includes a compatibleservice processor. For example, when a dual boot configured device bootsin a first operating system version, then a first service processor thatis compatible with that first operating system version is selected fornetwork access, and when the dual boot configured device boots in asecond operating system version, then the second service processor thatis compatible with that second operating system version is selected fornetwork access.

In some embodiments, initial network access for a device is directed toa service controller (e.g., service control 150), service processordownloader (e.g., service processor download 170), and/or similarnetwork element for managing service control. In some embodiments,initial network access is restricted to this initial network access tothe service controller, service processor downloader, and/or similarnetwork element for managing service control. In some embodiments, suchinitial network access is restricted until the device has been verifiedfor network access, as similarly discussed herein with respect tovarious embodiments. In some embodiments, such initial network access isrestricted until the device has been verified for network access and anappropriate service processor has been verified on the device and/ordownloaded and installed on the device, as similarly discussed hereinwith respect to various embodiments. In some embodiments, such initialnetwork access is restricted using various techniques, such as using afirst version of a service processor on the device that restricts suchinitial network access. In some embodiments, such initial network accessis restricted to and maintained in probation mode, as similarlydescribed herein (e.g., a restricted IP address can be used for theservice controller or other network element for service control insteadof the secured service controller IP addresses reserved for validatedand non-probation mode service processors, which, for example, canreduce the risks of various security risks, such as DoS, DDS, and/orother mass attacks against publicly or other more easily accessibleservice controller or download servers). For example, such initialnetwork access can include access to a common activation server, whichthe device can access for determination of a supported configuration fora new or second service processor image download. As another example,such initial network access can direct the device to an initial web pageincluding access to a service plan offer and purchase options (e.g.,providing for a device credential look up for device group, providechoices of programs to user, or other service plan offer and purchaseoptions). As another example, the initial web page can include access toa service plan offer and purchase options and a service processorverification and download/update function.

In some embodiments, a network based charging data record (CDR) feed, asdescribed herein with respect to various embodiments, is provided formonitoring service usage by managed devices. In some embodiments, theCDR feed includes device generated CDRs or micro-CDRs generated by theservice processor (e.g., service processor 115 can generate CDRs formonitored service usage on the device, which can, for at least someCDRs, include unique transaction codes for uniquely identifying themonitored service usage based on service or othercategorizations/criteria) on the device (e.g., a mobile device or anintermediate networking device for that mobile device). In someembodiments, the CDR feed is a real-time (e.g., near real-time) networkbased CDR feed provided for determining whether any devices have beencompromised (e.g., a hack of a first version or second version serviceprocessor providing for unrestricted service usage for such devices,and/or any other mass or security attack or vulnerability or exploit).For example, such a CDR feed can be used to determine abnormal orunusual traffic patterns and/or service level usage activities, which,for example, can be used to identify and/or protect against a DoS/DDSattack or other types of security attacks.

In some embodiments, based on various device and/or network basedmonitoring techniques, as described herein with respect to variousembodiments, a determination is made that the service processor (e.g.,service processor 115) is not functioning properly (e.g., may have beendamaged and/or compromised/tampered with and, for example, allowingnetwork access beyond the device's associated service plan and/or notproperly monitoring/billing for such service usage) and that anew/replacement service processor should be downloaded. In someembodiments, a new/replacement service processor can be downloaded andinstalled in such situations, using the various techniques describedherein with respect to various embodiments. In some embodiments, basedon various criteria (e.g., service usage monitoring, billing, and/or anyother criteria) or based on proactive and/or periodicadministrative/security measures, a new/replacement service processorcan be downloaded and installed, using the various techniques describedherein with respect to various embodiments.

In some embodiments, based on, for example, service plan changes (e.g.,user changes to their service plan), service provider changes (e.g.,service provider changes to their services/service policies or theassociated service plan), device changes (e.g., operating system versionor other software platform changes or various hardware changes), a newservice processor can be downloaded and installed or the installedservice processor can be updated, using the various techniques describedherein with respect to various embodiments.

FIG. 2 illustrates another wireless network architecture for providingDAS install techniques in accordance with some embodiments. As shown,FIG. 2 includes a 4G/3G/2G wireless network operated by, for example, acentral provider. As shown, various wireless mobile devices 100 are incommunication with base stations 125 for wireless network communicationwith the wireless network, and other devices 100 are in communicationwith Wi-Fi Access Points (APs) or Mesh 702 for wireless communication toWi-Fi Access CPE 704 in communication with central provider accessnetwork 109. In some embodiments, each of the mobile devices 100includes a service processor 115 (as shown), which, for example, can beinitially installed, downloaded, and/or updated service processors(e.g., first/second version service processor images) using serviceprocessor download function 170 as described herein, and each serviceprocessor 115 connects through a secure control plane link to a servicecontroller 122. In some embodiments, the service processor downloadfunction 170 is located elsewhere in the network or partially located inelsewhere or integrated with/as part of other network elements as willbe apparent to one of ordinary skill in the art in view of the variousembodiments disclosed herein.

In some embodiments, service usage information includes network basedservice usage information (e.g., charging data records (CDRs)), which isobtained from one or more network elements. In some embodiments, serviceusage information includes micro-CDRs provided by the service processor(e.g., service processor 115) installed on the device (e.g., mobiledevice 100). In some embodiments, micro-CDRs are used for CDR mediationor reconciliation that provides for service usage accounting on anydevice activity that is desired, as described herein with respect tovarious embodiments. In some embodiments, each device activity that isdesired to be associated with a billing event is assigned a micro-CDRtransaction code, and the service processor 115 is programmed to accountfor that activity associated with that transaction code. In someembodiments, the service processor 115 periodically reports (e.g.,during each heartbeat or based on any other periodic, push, and/or pullcommunication technique(s)) micro-CDR usage measures to, for example,the service controller 122 or some other network element. In someembodiments, the service controller 122 reformats the heartbeatmicro-CDR usage information into a valid CDR format (e.g., a CDR formatthat is used and can be processed by an SGSN or GGSN) and then transmitsit to an authorized network element for CDR mediation (e.g., CDRstorage, aggregation, mediation, feed 118, billing system 123, and/orbilling interface 127 or another authorized network element/function).In some embodiments, CDR mediation is used to account for the micro-CDRservice usage information by depositing it into an appropriate serviceusage account and deducting it from the user device bulk service usageaccount. For example, this technique provides for a flexible serviceusage billing solution that uses pre-existing solutions for CDRmediation and billing. For example, the billing system (e.g., billingsystem 123 and/or billing interface 127) processes the mediated CDR feedfrom CDR storage, aggregation, mediation, feed 118, applies theappropriate account billing codes to the aggregated micro-CDRinformation that was generated by the device, and then generates billingevents in a manner that does not require changes to billing systemsand/or billing infrastructure (e.g., using new transaction codes tolabel the new device assisted billing capabilities).

As shown in FIG. 2, a CDR storage, aggregation, mediation, feed 118 isprovided. In some embodiments, the CDR storage, aggregation, mediation,feed 118 receives, stores, aggregates and mediates micro-CDRs receivedfrom mobile devices 100. In some embodiments, the CDR storage,aggregation, mediation, feed 118 also provides a settlement platformusing the mediated micro-CDRs, as described herein with respect tovarious embodiments. In some embodiments, another network elementprovides the settlement platform using aggregated and/or mediatedmicro-CDRs (e.g., central billing interface 127 and/or another networkelement). In some embodiments, various techniques for partitioning ofdevice groups are used for partitioning the mobile devices 100 (e.g.,allocating a subset of mobile devices 100 for a distributor, an OEM, aMVNO, and/or another partner). As also shown in FIG. 2, a MVNO corenetwork 210 also includes a MVNO CDR storage, aggregation, mediation,feed 118, a MVNO billing interface 127, and a MVNO billing system 123.In some embodiments, the MVNO CDR storage, aggregation, mediation, feed118 receives, stores, aggregates and mediates micro-CDRs received frommobile devices 100 (e.g., MVNO group partitioned devices).

Those of ordinary skill in the art will appreciate that various othernetwork architectures can be used for providing DAS install techniques,and FIG. 2 is illustrative of just one such example network architecturefor which DAS install techniques described herein can be provided.

In some embodiments, CDR storage, aggregation, mediation, feed 118(e.g., service usage 118, including a billing aggregation data store andrules engine) is a functional descriptor for, in some embodiments, adevice/network level service usage information collection, aggregation,mediation, and reporting function located in one or more of thenetworking equipment apparatus/systems attached to one or more of thesub-networks shown in FIG. 2 (e.g., central provider access network 109and/or central provider core network 110), which is in communicationwith the service controller 122, and a central billing interface 127. Asshown, service usage 118 provides a function in communication with thecentral provider core network 110. In some embodiments, the CDR storage,aggregation, mediation, feed 118 function is located elsewhere in thenetwork or partially located in elsewhere or integrated with/as part ofother network elements. In some embodiments, CDR storage, aggregation,mediation, feed 118 functionality is located or partially located in theAAA server 121 and/or the mobile wireless center/Home Location Register(HLR) 132 (as shown, in communication with a DNS/DHCP server 126). Insome embodiments, service usage 118 functionality is located orpartially located in the base station, base station controller and/orbase station aggregator, collectively referred to as base station 125 inFIG. 2. In some embodiments, CDR storage, aggregation, mediation, feed118 functionality is located or partially located in a networkingcomponent in the central provider access network 109, a networkingcomponent in the core network 110, the central billing system 123, thecentral billing interface 127, and/or in another network component orfunction. This discussion on the possible locations for the networkbased and device based service usage information collection,aggregation, mediation, and reporting function (e.g., CDR storage,aggregation, mediation, feed 118) can be easily generalized as describedherein and as shown in the other figures described herein as would beapparent to one of ordinary skill in the art. Also as shown in FIG. 2,the service controller 122 is in communication with the central billinginterface 127 (also sometimes referred to as the external billingmanagement interface or billing communication interface), which is incommunication with the central billing system 123. As shown, an ordermanagement 180 and a subscriber management 182 are also in communicationwith the central provider core network 110 for facilitating order andsubscriber management of services for the devices 100 in accordance withsome embodiments, and a network provisioning system 162 is also providedin communication with the central provider core network 110 forfacilitating network provisioning functions.

In some embodiments, the CDR storage, aggregation, mediation, feed 118(and/or other network elements or combinations of network elements)provides a device/network level service usage information collection,aggregation, mediation, and reporting function. In some embodiments, theCDR storage, aggregation, mediation, feed 118 (and/or other networkelements or combinations of network elements) collects device generatedusage information for one or more devices on the wireless network (e.g.,devices 100); and provides the device generated usage information in asyntax and a communication protocol that can be used by the wirelessnetwork to augment or replace network generated usage information forthe one or more devices on the wireless network. In some embodiments,the syntax is a charging data record (CDR), and the communicationprotocol is selected from one or more of the following: 3GPP, 3GPP2, orother communication protocols. In some embodiments, as described herein,the CDR storage, aggregation, mediation, feed 118 collects/receivesmicro-CDRs for one or more devices on the wireless network (e.g.,devices 100). In some embodiments, the CDR storage, aggregation,mediation, feed 118 (and/or other network elements or combinations ofnetwork elements) includes a service usage data store (e.g., a billingaggregator) and a rules engine for aggregating the collected devicegenerated usage information. In some embodiments, the network device isa CDR feed aggregator, and the CDR storage, aggregation, mediation, feed118 (and/or other network elements or combinations of network elements)also aggregates CDRs and/or micro-CDRs for the one or more devices onthe wireless network; applies a set of rules to the aggregated CDRsand/or micro-CDRs using a rules engine (e.g., bill by account,transactional billing, revenue sharing model, and/or any other billingor other rules for service usage information collection, aggregation,mediation, and reporting), and communicates a new set of CDRs for theone or more devices on the wireless network to a billing interface or abilling system (e.g., providing a CDR with a billing offset byaccount/service).

In some embodiments, the CDR storage, aggregation, mediation, feed 118(and/or other network elements or combinations of network elements)communicates a new set of CDRs (e.g., aggregated and mediated CDRsand/or micro-CDRs that are then translated into standard CDRs) for theone or more devices on the wireless network to a billing interface(e.g., central billing interface 127) or a billing system (e.g., centralbilling system 123). In some embodiments, the CDR storage, aggregation,mediation, feed 118 (and/or other network elements or combinations ofnetwork elements) communicates with a service controller (e.g., servicecontroller 122) to collect the device generated usage information (e.g.,micro-CDRs) for the one or more devices on the wireless network. In someembodiments, the CDR storage, aggregation, mediation, feed 118 (and/orother network elements or combinations of network elements) communicateswith a service controller, in which the service controller is incommunication with a billing interface or a billing system. In someembodiments, the CDR storage, aggregation, mediation, feed 118 (and/orother network elements or combinations of network elements) communicatesthe device generated usage information to a billing interface or abilling system. In some embodiments, the CDR storage, aggregation,mediation, feed 118 (and/or other network elements or combinations ofnetwork elements) communicates with a transport gateway (not shown)and/or a Radio Access Network (RAN) gateway (not shown) to collect thenetwork generated usage information for the one or more devices on thewireless network. In some embodiments, the service controller 122communicates the device generated service usage information (e.g.,micro-CDRs) to the CDR storage, aggregation, mediation, feed 118 (and/orother network elements or combinations of network elements).

In some embodiments, the CDR storage, aggregation, mediation, feed 118(and/or other network elements or combinations of network elements)performs rules for performing a bill by account aggregation andmediation function. In some embodiments, the CDR storage, aggregation,mediation, feed 118 (and/or other network elements or combinations ofnetwork elements) performs rules for performing a service billingfunction, as described herein, and/or for performing aservice/transactional revenue sharing function, as described herein. Insome embodiments, the service controller 122 in communication with theCDR storage, aggregation, mediation, feed 118 (and/or other networkelements or combinations of network elements) performs a rules enginefor aggregating and mediating the device generated usage information(e.g., micro-CDRs). In some embodiments, a rules engine device incommunication with the CDR storage, aggregation, mediation, feed 118(and/or other network elements or combinations of network elements)performs a rules engine for aggregating and mediating the devicegenerated usage information.

In some embodiments, the rules engine is included in (e.g., integratedwith/part of) the CDR storage, aggregation, mediation, feed 118. In someembodiments, the rules engine and associated functions, as discussedherein, is a separate function/device. In some embodiments, the servicecontroller 122 performs some or all of these rules engine basedfunctions, as discussed herein, and communicates with the centralbilling interface 127. In some embodiments, the service controller 122performs some or all of these rules engine based functions, as discussedherein, and communicates with the central billing system 123.

In some embodiments, duplicate CDRs are sent from the network equipmentto the billing system 123 that is used for generating service billing.In some embodiments, duplicate CDRs are filtered to send only thoseCDRs/records for devices controlled by the service controller and/orservice processor (e.g., managed devices). For example, this approachcan provide for the same level of reporting, lower level of reporting,and/or higher level of reporting as compared to the reporting requiredby the central billing system 123.

In some embodiments, the service controller 122 sends the devicegenerated CDRs to the rules engine (e.g., service usage 118), and therules engine applies one or more rules, such as those described hereinand/or any other billing/service usage related rules as would beapparent to one of ordinary skill in the art. In some embodiments, theservice controller 122 generates CDRs similar to other network elements,and the rules (e.g., bill-by-account) are performed in the centralbilling interface 127. For example, for the service controller 122 togenerate CDRs similar to other network elements, in some embodiments,the service controller 122 is provisioned on the wireless network andbehaves substantially similar to other CDR generators on the network) aswould be apparent to one of ordinary skill in the art.

In some embodiments, the service controller 122 is provisioned as a newtype of networking function that is recognized as a valid and securesource for CDRs by the other necessary elements in the network (e.g.,CDR storage, aggregation, mediation, feed 118). In some embodiments,where the network necessary apparatus will only recognize CDRs fromcertain types of networking equipment (e.g. a RAN gateway or transportgateway), then the service controller 122 can provide authenticationcredentials to the other networking equipment that indicate it is one ofthe approved types of equipment. In some embodiments, the link betweenthe service controller 122 and the necessary CDR aggregation andmediation equipment is secured, authenticated, encrypted, and/or signed.

In some embodiments, the CDR storage, aggregation, mediation, feed 118discards the network based service usage information (e.g., networkbased CDRs) received from one or more network elements. In theseembodiments, the service controller 122 can provide the device basedservice usage information (e.g., device based CDRs or micro-CDRs) to theCDR storage, aggregation, mediation, feed 118 (e.g., the CDR storage,aggregation, mediation, feed 118 can just provide a store, aggregate,and communication function(s)), and the device based service usageinformation is provided to the central billing interface 127 or thecentral billing system 123.

In some embodiments, the device based CDRs (e.g., micro-CDRs) and/or newCDRs generated based on execution of a rules engine as described hereinare provided only for devices that are managed and/or based on devicegroup, service plan, or any other criteria, categorization, and/orgrouping, such as based on ambient service or ambient service provideror transactional service or transactional service provider.

In some embodiments, based on, for example, service plan changes (e.g.,user changes to their service plan), service provider changes (e.g.,service provider changes to their services/service policies or theassociated service plan), micro-CDR transaction code changes, and/or anyother related changes, a new service processor can be downloaded andinstalled or the installed service processor can be updated to allow,for example, the tracking of one or more service usage activities by thedevice using micro-CDRs (e.g., for new or previouslyunmonitored/untracked service usage activities, using, for example, newor updated micro-CDR transaction codes (uniquely) associated with suchservice usage activities), using the various techniques described hereinwith respect to various embodiments.

FIG. 3 illustrates a flow diagram for DAS install techniques inaccordance with some embodiments. At 302, the process begins. At 304,whether a device (e.g., mobile device 100) is in a device group isdetermined. At 306, whether the device includes a service processor isdetermined. If so, at 308, then the installed service processor isverified (e.g., up to date and/or validated for that device, devicegroup, and/or associated service plan) and network access is allowed(e.g., managed/monitored by the installed and verified service processoraccording to the associated service plan for the device). Otherwise(e.g., the device does not have an installed service processor), at 310,then an appropriate service processor for the device is determined(e.g., based on the device type, device group, and/or version, such ashardware/software platform of the device, an associated service plan,service provider, and/or any other criteria or settings). At 312, theservice processor is downloaded and installed (e.g., using a bootstrapprocess or other techniques, as described herein with respect to variousembodiments) and network access is allowed (e.g., managed/monitored bythe installed service processor according to the associated service planfor the device).

In some embodiments, the device is also directed to, for example, anactivation server to, for example, authenticate the device and/or verifya service processor for the device (e.g., ensure that a current andverified service processor version is installed and/or download acurrent and verified service processor version for the device) prior toallowing such network access. For example, a DAS install client can bedownloaded (e.g., using bootstrapping or other/similar techniques, froma download server and/or from a website) that allows for secureconnection from the device (e.g., mobile device 100) to a securedownload server (e.g., service processor download 170) (e.g., supportfor a configuration of the device is determined, such as through adevice query or device download of client verification software can beused to verify the device hardware/software configuration). In thisexample, a user/device validation step can also be performed. Forexample, an authorization process for a user sign-up can be performed(e.g., based on a user name, MAC address, Turing machine textverification, credit card verification, and/or otherauthorization/validation techniques), in which this can be performedautomatically or the user/device can be required to enter certaincredentials for authorization/validation. In some embodiments, theauthorization process also includes various techniques for associating auser's identity with the device (e.g., using public key/TLS techniques,SSH techniques for TLS, and/or identity management techniques). In thisexample, a check can also be performed to determine if the device waspreviously and/or is currently an activated device (e.g., the device isalready associated with a service plan). For example, whether the devicebelongs to a registered device group can be determined, and if not, thenthe default settings for that type of device can be applied. In someembodiments, the service processor is encrypted, hashed, and/orobfuscated based on the previous determination (e.g., device groupassociation and/or default device settings). In some embodiments, if thedevice is not associated with a service plan (e.g., based on the devicelook-up using device based unique identifier(s)/credential(s), asdescribed herein), then the device can be redirected to a service portalfor an activation offer for a service plan (e.g., using an activationserver). In some embodiments, the portal utilizes header information toindicate that the device is a managed device (e.g., for a given serviceprovider, MVNO, or other service partner) in the portal request to proxyto an appropriate proxy server for that service provider for theactivation process. At 314, the process is completed.

FIG. 4 illustrates another flow diagram for DAS install techniques inaccordance with some embodiments. At 402, the process begins. At 404,whether a device (e.g., mobile device 100) is in a device group isdetermined (e.g., or other list that indicates that this device includesan installed, up to date, and/or validated service processor, and, forexample, to also verify that the SIM, ESN, or other unique deviceidentifier is registered, such as in an HLR/NIR database, as associatedwith service settings/policies for that device for service access). At406, whether the device includes a first version service processor isdetermined. If not (e.g., the device does not have an installed firstversion service processor), at 408, then a new service processor isdownloaded (e.g., as similarly discussed above with respect to FIG. 3)and network access is allowed (e.g., managed/monitored by the installednew service processor according to the associated service plan for thedevice). Otherwise (e.g., the device includes an installed first versionservice processor), then at 409, an appropriate second version serviceprocessor for the device is determined (e.g., based on the device typeand version, such as hardware/software platform, device group, anassociated service plan, service provider, and/or any other criteria orsettings). At 412, the second version service processor (e.g., securedfor the device, using various techniques, as described herein) isdownloaded and installed (e.g., using bootstrapping or other/similartechniques, as described herein), or in some embodiments, the firstversion of the service processor is updated to provide a second versionservice processor uniquely associated with the device, and networkaccess is allowed (e.g., managed/monitored by the installed secondversion service processor according to the associated service plan forthe device). At 414, the process is completed.

FIG. 5 illustrates another flow diagram for DAS install techniques inaccordance with some embodiments. At 502, the process begins. At 504,whether a device (e.g., mobile device 100) is in a device group isdetermined (e.g., as similarly described above with respect to FIG. 3).At 506, whether the device includes a first version service processor isdetermined. If not (e.g., the device does not have an installed firstversion service processor), at 508, then a new service processor isdownloaded (e.g., as similarly discussed above with respect to FIG. 3)and network access is allowed (e.g., managed/monitored by the installednew service processor according to the associated service plan for thedevice). Otherwise (e.g., the device includes an installed first versionservice processor), at 510, then an appropriate second version serviceprocessor for the device is determined (e.g., based on the device typeand version, such as hardware/software platform, device group, anassociated service plan, service provider, and/or any other criteria orsettings). At 512, the second version service processor (e.g., securedusing various techniques, as described herein) is downloaded andinstalled (e.g., using a bootstrap process or other/similar techniques,as described herein). At 514, network access is allowed in probationmode, as described herein with respect to various embodiments. Forexample, the device can be managed in probation mode after thenew/second version service processor install (e.g., service controlcommunication can be limited to a particular set of probation mode IPaddresses that can be used for the service controller or other networkelement for service control instead of the secured service controller IPaddresses reserved for validated and non-probation mode serviceprocessors, which, for example, can reduce the risks of various securityrisks, such as DoS, DDS, or other mass or other security attacks againstpublicly or other more easily accessible service controller or downloadservers). In some embodiments, while in probation mode, the serviceprocessor executes more robust service monitoring techniques (e.g., morefrequent and/or more robust service integrity checks and/or morefrequent heartbeats, for example, to monitor actual device/user behaviorwith the associated expected behavior). At 516, after the probationperiod is completed (e.g., based on time, monitored activities, and/orany other criteria), network access is allowed in normal mode (e.g., thedevice is no longer operating in the probation mode, as describedherein). For example, after a probation period is completed (e.g., basedon time, monitored activities, and/or any other criteria), the device isprovided access based on the associated service plan, which is managed,at least in part, by the service processor in communication with, forexample, a service controller or other network element for servicecontrol. At 518, the process is completed.

In some embodiments, the device OS requires a pre-registered and signedversion of the service processor software in order for the OS to allowthe service processor to be installed or updated. In such embodiments, asequence of pre-registered, pre-signed service processor softwareversions that have differing security parameters (e.g. encryption,signature, obfuscation, differences in code sequences, information forquery-response sequences, and/or other security parameters) areprovided. In some embodiments, the pre-registered service processors areused to regularly update the service processor software for a portion ofdevices connected to the network, or for all devices connected to thenetwork. In some embodiments, a specific version of the serviceprocessor is assigned to a given device, and other versions with othersecurity parameters will not be allowed to obtain service from thenetwork. For example, more than one version of the software can beregistered and distributed at any one time so that a hacker cannotcreate code that works for all devices. A sequence of service processorversions can be held in reserve and deployed when a successful softwarehack version is detected in the field for one or more previous serviceprocessor versions, and the new versions that have been held in reservecan be used to update devices in the field. As the reserved versionshave not yet been distributed prior to the detection of a successfulhack, it is not possible for a hacker to have a hacked version of thenew software, and by refreshing new versions on a frequent basis it canbecome impossible for a hacker to successfully hack the new versionsbefore additional new versions are deployed. Such embodiments can buytime by keeping successful software hacks out of the devices in thefield until the successful software hack can be analyzed and asystematic security solution implemented to prevent the hack fromremaining effective.

In some embodiments not all of the service processor software ismodified into pre-registered modified security configuration versionsthat are regularly refreshed, but instead a portion of the serviceprocessor software that includes unique security information (e.g.,security keys, signatures and/or responses to secure queries, and/orother security information, and/or the capability to analyze theintegrity of the other service processor software). In this manner, whena device is suspected of being hacked the new service processor softwareportion with different security configuration can be updated and used toascertain the integrity of the existing service processor configuration,which makes the update process shorter and lower bandwidth.

Clause 1: A system, comprising a processor of a network deviceconfigured to: determine if a communications device in communicationwith a wireless network includes a service processor for assistingcontrol of the communications device use of a service on the wirelessnetwork, wherein the service processor includes a service profile thatincludes a plurality of service policy settings, and wherein the serviceprofile is associated with a service plan that provides for access tothe service; and verify the service processor; and a memory of thenetwork device coupled to the processor and configured to provide theprocessor with instructions.

The system recited in clause 1, wherein the service policy settingsinclude one or more of the following: access control settings, trafficcontrol settings, billing system settings, user notification withacknowledgment settings, user notification with synchronized serviceusage information, user privacy settings, user preference settings,authentication settings, admission control settings, application accesssettings, content access settings, transaction settings, and network ordevice management communication settings.

Although the foregoing embodiments have been described in some detailfor purposes of clarity of understanding, the invention is not limitedto the details provided. There are many alternative ways of implementingthe invention. The disclosed embodiments are illustrative and notrestrictive.

INCORPORATION BY REFERENCE

This application incorporates by reference the following for allpurposes:

Application Ser. No. 14/158,206, entitled DEVICE ASSISTED SERVICESINSTALL, filed Jan. 17, 2014; application Ser. No. 13/674,808, entitledDEVICE ASSISTED SERVICES INSTALL, filed Nov. 12, 2012; application Ser.No. 12/694,455, entitled DEVICE ASSISTED SERVICES INSTALL, filed Jan.27, 2010; application Ser. No. 12/380,780, entitled AUTOMATED DEVICEPROVISIONING AND ACTIVATION, filed Mar. 2, 2009; provisional ApplicationNo. 61/206,354, entitled SERVICES POLICY COMMUNICATION SYSTEM ANDMETHOD, filed Jan. 28, 2009; provisional Application No. 61/206,944,entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD, filed Feb. 4,2009; provisional Application No. 61/207,393, entitled SERVICES POLICYCOMMUNICATION SYSTEM AND METHOD filed Feb. 10, 2009; provisionalApplication No. 61/207,739, entitled SERVICES POLICY COMMUNICATIONSYSTEM AND METHOD filed Feb. 13, 2009; and provisional Application No.61/264,120, entitled DEVICE ASSISTED SERVICES INSTALL filed Nov. 24,2009.

What is claimed is:
 1. A method of automatically configuring wirelessdata service, executed by a processor on a wireless end-user device,comprising: establishing communication, via a wireless wide area network(WWAN) modem and a WWAN, with a wireless service control networkelement, executing a first version service processor, not specific to aparticular wireless service provider, to facilitate downloading, overthe WWAN to the device, storable computer instructions for a secondversion service processor from the wireless service control networkelement, the second version service processor specific to the particularwireless service provider, installing the downloaded second versionservice processor on the wireless end-user device, operating the devicewith the second version service processor in a probationary mode thatrestricts WWAN data access, and upon validation of proper operation ofthe device with the second version service processor in the probationarymode, operating the device with the second version service processor ina normal mode that allows WWAN data access according to a user serviceplan associated with the particular wireless service provider.
 2. Themethod of claim 1, wherein the wireless service control network elementis associated with the particular wireless service provider.
 3. Themethod of claim 1, wherein the first version service processor includesa policy setting associated with the use of the WWAN modem, the policysetting to assist in limiting or directing WWAN data access by thedevice to access to a service control element, a service processordownload element, and/or a service policies and accounting function. 4.The method of claim 1, wherein establishing communication with thewireless service control network element comprises the first versionservice processor supplying a device credential to the wireless servicecontrol network element.
 5. The method of claim 1, further comprisingthe first version service processor communicating a user selection of aservice plan to the wireless service control network element.
 6. Themethod of claim 5, wherein the second version service processor differsbased on the user selection of a service plan.
 7. The method of claim 1,wherein the first version service processor is a version that ispre-installed during manufacture or distribution of the wirelessend-user device.
 8. The method of claim 1, further comprising the secondversion service processor generating service usage information andsupplying the generated service usage information to a network elementperforming the validation of the proper operation of the device.
 9. Themethod of claim 1, wherein operating the device in the probationary modecomprises allowing WWAN data access with service monitoring greater thana service monitoring that occurs during the normal mode.
 10. The methodof claim 1, wherein operating the device in the probationary modecomprises limiting WWAN data access in a way not so limited in thenormal mode, based on one or more of the following limits: a period oftime for data access, a network address limitation, a service typelimitation, a content type limitation, a device application typelimitation, a bandwidth limitation, and a data usage limitation.
 11. Themethod of claim 1, wherein the second version service processor isuniquely associated with the wireless end-user device based on one ormore device credentials of the wireless end-user device.
 12. The methodof claim 1, wherein the second version service processor is uniquelyassociated with the wireless end-user device based on one or more devicecredentials of the wireless end-user device and based on userinformation associated with a temporary user account.
 13. The method ofclaim 1, wherein the second version service processor is uniquelyassociated with the wireless end-user device, a device user, a devicegroup, or a service plan.
 14. The method of claim 1, wherein operatingthe device with the second version service processor in the normal modecomprises using one or more restricted Internet protocol (IP) addressesproviding for network access to a service controller reserved fornon-probationary mode service processors.
 15. The method of claim 1,further comprising the first version service processor limiting dataaccess to the WWAN for purposes of wireless service control andselection of a user service plan, and wherein the second version serviceprocessor is based on a service plan selection for the communicationsdevice.
 16. The method of claim 1, wherein executing the first versionservice processor to facilitate downloading is based on a commandreceived from a network element that detects a need for the device toinstall a second version service processor.
 17. The method of claim 1,further comprising cooperating with the network wireless service controlelement to determine a device group to which the wireless end-userdevice is assigned, the second version service processor based on thedevice group.